gpg --list-config change ahead

Bernhard Reiter bernhard at
Wed Dec 15 10:14:59 CET 2010

Am Donnerstag, 2. Dezember 2010 15:53:12 schrieb Werner Koch:
> In response to Bernhard's question I changed GnuPG 2.1 to print "AES128"
> instead of just "AES".  There is one little problem: shall we do this
> also for the --list-config option?  It will now print
>   $ gpg2 --list-config --with-colons ciphername
>   cfg:ciphername:3DES;CAST5;BLOWFISH;AES128;AES192;AES256;[...]

I wonder: Shouldn't this be accessible by gpgconf as well?
If it should not, at least a hint in the documentation of gpgconf would be 
nice, I was reading this lately to see if I could find out all the valid 
values for some of the options that gpgconf can set. So the hint would have 
been useful to me.

Managing Director - Owner:       (Free Software Company)
Deputy Coordinator Germany: Board member:
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20101215/e7ac2547/attachment.pgp>

More information about the Gnupg-devel mailing list