Personally I'd advise against this until NIST publishes test vectors for the finalist.We already have:DES(_OLD) and DES.SHA0 and SHA1Rjindael and AES.NIST has a long track record of changing algorithms before going 'final' and the problem is that once people start using the 'bad' version of the algorithm, it has to be supported forever, and that causes interop AND security issues.If you really want to speed the adoption of SHA3 :), ask NIST to finalize the standard ?, until that happens it's a poison pill.Peter-owner-openssl-...@openssl.org wrote: -To: openssl DEV openssl-dev@openssl.orgFrom: Francis GASCHET <f...@numlog.fr>Sent by: owner-openssl-...@openssl.orgDate: 02/12/2014 08:45PMSubject: SHA-3 availability
Dear all,
The OFTP2 support group is going to
start upgrading the cipher suite supported in OFTP2.
The proposal includes SHA-3, which
is supported by Java implementations (BouncyCastle
at least).
Is there some plan to support it
in openSSL ?
Thanks and best regards,
--