And Java implementations as well.
replyUS Government is starting to push hard so code first needs to support it.
replyOk, but when is it coming to our web browsers and email clients?
replyI don't know about mail clients, but it's in most web browsers already.
replyThen I'm wondering why they don't simply use the same crypto libraries as the web browsers.
replyChromium uses BoringSSL, which opens its readme as follows:
reply> BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
> Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
OpenSSL itself is a clusterfuck that doesn't really meet anyone's needs: https://cryptography.io/en/latest/statements/state-of-openss...
Go features cleaner crypto APIs (than OpenSSL for example) with less footguns.
replyPreventing CGO overhead maybe?
replyIt’s been on by default for 2 years in Chrome.
reply