Hi Peter
thanks a lot for you Answer!
Most Companies already have X.509 certs and therefore it would be great if they can just use them.
It does not make sense to manage another kind of certs just because applications that suport/use GnuPG did not added gpgsm support.
Therefore I'm pretty sure it was a conceptual error to support X.509 in another tool. If X.509 were added into gpg, then every application would immediately had support for both worlds :-)
The gpgme project tries to fix the error of splitting both worlds into two tools and it is possible to implement it into applications. But... every application must be changed. And because there are not many applicatons which have changed to use gpgme proofs that it's too much work.
Btw.: in the long turn it does not make sense to support / develop two Tools (gpg.exe and gpgsm.exe) and in parallel, support / develop gpgme to join the 'splitted tools'.
Instead of changing dozens of applications it would be easier to change the common part: merge gpg.exe und gpgsm.exe :-)
I made a test with Git: I just renamed gpgsm.exe to gpg.exe. It worked perfectly!
Kind regards,
Tom
thanks a lot for you Answer!
Most Companies already have X.509 certs and therefore it would be great if they can just use them.
It does not make sense to manage another kind of certs just because applications that suport/use GnuPG did not added gpgsm support.
Therefore I'm pretty sure it was a conceptual error to support X.509 in another tool. If X.509 were added into gpg, then every application would immediately had support for both worlds :-)
The gpgme project tries to fix the error of splitting both worlds into two tools and it is possible to implement it into applications. But... every application must be changed. And because there are not many applicatons which have changed to use gpgme proofs that it's too much work.
Btw.: in the long turn it does not make sense to support / develop two Tools (gpg.exe and gpgsm.exe) and in parallel, support / develop gpgme to join the 'splitted tools'.
Instead of changing dozens of applications it would be easier to change the common part: merge gpg.exe und gpgsm.exe :-)
I made a test with Git: I just renamed gpgsm.exe to gpg.exe. It worked perfectly!
Kind regards,
Tom
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
