GOST support in GnuPG

Werner Koch wk at gnupg.org
Wed Apr 10 20:42:09 CEST 2019


On Wed, 10 Apr 2019 20:56, manowar at altlinux.org said:

>   Hi again. My question is still unanswered. Are there some guidelines
> about adding new key types, curves, ciphers, etc. to GnuPG I should keep
> to when making such changes?

Aside from doc/HACKING there are no fixed rules.  However adding new
algorithms etc requires that they are part of the implemented standard
and further we need to see whether it makese sense to implement and
_maintain_ them.

>>   My current set of patches are as follows:

I briefly looked at your patches but concluded that this is a log of new
code for just another algorithm.  Thus your patches requires a closer
look.  Right now I do not have the time for this and unless there is a
reason to tag it at high priority, I doubt that I can look at it in the
next weeks.

A reason for this might be that we can foster deployment of OpenPGP in
certain domains.  However, if it turns out that GOST as been weakened on
purpose, there is no chance that it can part of _gpg_ (ie. to OpenPGP).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20190410/6e43a751/attachment.sig>

More information about the Gnupg-devel mailing list