gpg --list-config change ahead

Werner Koch wk at
Thu Dec 2 15:53:12 CET 2010


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

instead of 

  $ gpg2 --list-config --with-colons ciphername

Does anyone expect a real problem with this change?  I think the most
popular user is Enigmail - any problem to expect?

Note that GPG still accepts "AES" as input (as well as "AES128" and
"AES-128"); only the way we print the name changed.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gnupg-devel mailing list