Renaming AES to AES-128

[smu johnson]

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.

On Mon, Nov 29, 2010 at 9:15 AM, Bernhard Reiter <bernhard at intevation.de>wrote:

> What about renaming "AES" to "AES-128" in libgcrypt?
> Currently a user cannot see to what keylength AES refers to and some
> might believe it could be 256. So there is a potential for confusion
> which is something a security aware software should avoid of course.
>
> The code is in:
>
> http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/tags/libgcrypt-1.4.4/cipher/rijndael.c?revision=1383&root=Libgcrypt&view=markup
>
> AES128 and AES-128 already exist as aliases for "AES".
>
> Opinions?
>
> Bernhard
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20101129/c508c181/attachment-0001.htm>