Renaming AES to AES-128

David Shaw dshaw at
Thu Dec 2 16:42:36 CET 2010

On Nov 29, 2010, at 3:31 PM, smu johnson wrote:

> Although I have read Werner's comments, I also think this is a great idea.  The same with Blowfish for GnuPG which is uses 128 bit keys, and Twofish with 256.  CAMELLIA128 has its blocksize next to it, but not the others.  In addition, as you noticed, the namings where only 2 of the 3 Rijndael ciphers have the bitsize in:  AES, AES196, AES256 looks a bit ramshackle and slapped together.  I am not a fan of this inconsistency either.

It's historical - those are the names used by the RFC.  User presentation of the underlying ciphers is pretty much up to the implementation, and so can (and do) vary somewhat.  For example, GnuPG has a cipher called CAST5.  PGP calls it CAST (no "5").  PGP calls a 256-bit AES "AES-256" while GnuPG calls it "AES256" (no hyphen), etc.

Making a change like this in GnuPG is easier than for a library like libgcrypt.


More information about the Gnupg-devel mailing list