Package: gnupg
Version: 1.4.12-7+deb7u7
When generating a new key pair, gpg sets the digest algorithm to the
default SHA1 and completely ignores non-default settings specified
with s2k-digest-algo.
This happens both when specified on the commandline:
gpg --s2k-digest-algo SHA256 --gen-key
or when specified in the config file ~/.gnupg/gpg.conf
s2k-digest-algo SHA256
After the key has been generated, gpg --list-packets shows
iter+salt S2K, algo: 3, SHA1 protection, hash: 8, salt: blablabla
I have tried using SHA256 and SHA512, both are ignored, even though
both are listed as supported when invoked
gpg --version
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
