Open bkmgit opened 10 months ago
The latest comment on the openssl ticket
I still don't see an RFC for Blake3 available, so this seems like its not going to get planned.
Marking as inactive, to be closed at the end of 3.4 dev barring further input
Associated repository https://github.com/BLAKE3-team/BLAKE3-IETF
Transferring this from https://github.com/BLAKE3-team/BLAKE3/issues/347 created by @dralley
The OpenSSL project states that "a necessary condition to include a new algorithm into the main code base is that the algorithm should be part of a standard from a recognized standardization body", and also that "Informational RFCs are sufficient for adopting an algorithm by OpenSSL."
https://github.com/openssl/openssl/issues/11613
It would be great to (eventually) see an implementation of Blake3 in OpenSSL, because that would open the door to it being included in places like the Python standard library. It seems like they might be open to it, but this would be a prerequisite.
As an example here is the informational RFC for Blake 2 https://www.rfc-editor.org/rfc/rfc7693.html