Renaming AES to AES-128

Bernhard Reiter bernhard at
Tue Nov 30 14:40:37 CET 2010

Am Montag, 29. November 2010 21:01:28 schrieb Werner Koch:
> Libgcrypt happily accepts AES-128 as an alias for AES.  However if we
> map the internal identifier back to a name we need to pich one and that
> happens to be "AES" for 9 years now.  Changing this is an ABI break and
> thus not justified.

Leaving the primary identifier like it was, is a source of confusion
which also has a cost. What is the cost and consequences of the ABI change?

We could keep "AES" as an alias for backwards compatibility and mark it as 
deprecated so it will go away after X years. Could there be software that 
would still stumble then?

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/20101130/93d60da8/attachment.pgp>

More information about the Gnupg-devel mailing list