Jump to content

Talk:AES implementations

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 79.171.96.132 (talk) at 16:52, 19 October 2011 (Suggest removing wrapper libraries that do not implement the AES algorithm themselves). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconCryptography: Computer science Unassessed
WikiProject iconThis article is within the scope of WikiProject Cryptography, a collaborative effort to improve the coverage of Cryptography on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
???This article has not yet received a rating on Wikipedia's content assessment scale.
???This article has not yet received a rating on the importance scale.
Taskforce icon
This article is supported by WikiProject Computer science.

GnuTLS

I'm opening discussion for the inclusion of GnuTLS as a C implementation of AES. It performs more or less as a drop in for OpenSSL. Quoted from the GnuTLS page: "GnuTLS is a secure communications library. It provides a C language application programming interface (API) to access security protocols such as IETF's transport layer security (TLS) protocols." I'm going to add the library, anyone feel free to provide counterpoint to it's inclusion though.

Tului (talk) 04:09, 11 June 2011 (UTC)[reply]

no pycrypt

there is no longer a functioning pycrypt module being posted on the link given. — Preceding unsigned comment added by 213.105.62.2 (talk) 09:04, 30 August 2011 (UTC)[reply]


Removing wrappers

I suggest removing all the libraries that merely wrap other implementations. These are not AES implementations in and of themselves, though they can be very useful for development. This includes M2Crypto, NCrypt, pycryptopp and probably more.