-
Notifications
You must be signed in to change notification settings - Fork 178
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
0.23.0
tls
feature relies on rustls-platform-verifier
, bringing other unwanted dependencies
#1407
Comments
hmm, lemme a have look. You are correct, we need another feature for |
@niklasad1 I'm taking a stab at this, what I'm currently thinking is having only two features:
At least those two are the only ones I have in need right, only having an option to not rely on the rustls-platform-verifier, while still allowing the tls flow. Please let me know if you had others in mind. |
Yeah I think the following would be good:
|
@niklasad1 I did an initial approach here: #1419, please let me know what you think. |
In
0.23.0
the newtls
feature brings all:["tokio-rustls", "rustls-pki-types", "rustls-platform-verifier", "rustls"]
, which ends up bringingrustls-native-certs
, and thenopenssl-probe
. Even when usingCertificateStore::Custom
it's still requirestls
feature, which will requirerustls-platform-verifier
.Please let me know if missed something, but is there a way to still use
tls
without depending completely onrustls-platform-verifier
?The text was updated successfully, but these errors were encountered: