-
-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding BearSSL #300
Comments
BearSSL development appears to have stalled. I'm no longer confident that adding it is advisable. |
I'm closing this as wontfix. The issue here is that BearSSL has stalled out, and there seems to be no clear path to TLS v1.3 which has been fully standardized for a while now. I don't want to burn cycles supporting software that only supports legacy protocols. |
(Btw, if BearSSL is resurrected, then I might take it up again.) |
picoTLS looks interesting as an alternative as well, but I think it requires another cryptographic library. |
BearSSL is an alternate, small, MIT licensed TLS library. (It actually only implements TLS, not SSL.)
https://bearssl.org/
This beta quality, but it should be sufficient for our needs. (It may not be as efficient as mbedTLS, but I like to have the ability to include a vendored projected automatically.)
The text was updated successfully, but these errors were encountered: