-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add http-rustls feature #466
Conversation
Nice, thanks! |
A new OpenSSL release comes out tomorrow, that fixes yet another critical security issue:
it would be great to get rid of OpenSSL with this PR. |
@toxeus do you mind addressing build issues? |
@tomusdrw done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I thought of making this default, but I think ws-tls
will pull in openssl anyway, right?
Could you also update the README to mention how to get a no-openssl build?
Yes, our troublemaker crate is pulling in openssl 😉 I have updated the README. |
The existing `http-tls` feature enables TLS support via `hyper-tls` which in turn pulls in OpenSSL on Linux via `native-tls`. OpenSSL is written in C and has a long history of vulnerabilities caused by memory corruption. The new `http-rustls` feature allows to choose a TLS implementation that is written in Rust.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, thanks!
The existing
http-tls
feature enables TLS support viahyper-tls
which in turn pulls in OpenSSL on Linux vianative-tls
. OpenSSL is written in C and has a long history of vulnerabilities caused by memory corruption.The new
http-rustls
feature allows to choose a TLS implementation that is written in Rust.Depends on #454 being merged first. I'll rebase once that happens.