-
Notifications
You must be signed in to change notification settings - Fork 87
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
test fails without feature tls12 #107
Comments
What test command are you running? |
Sorry, I forgot to copy that and no longer have that build log lying around - but it was likely I am packaging this crate for Debian, and run tests in various feature combinations. |
This one-line fix solved the issue for me: https://salsa.debian.org/debian/rust-tokio-rustls/-/blob/debian/latest/debian/patches/1001_tls12.patch --- a/tokio-rustls/tests/badssl.rs
+++ b/tokio-rustls/tests/badssl.rs
@@ -32,6 +32,7 @@
}
#[tokio::test]
+#[cfg(feature = "tls12")]
async fn test_tls12() -> io::Result<()> {
let mut root_store = rustls::RootCertStore::empty();
root_store.add_server_trust_anchors(webpki_roots::TLS_SERVER_ROOTS.0.iter().map(|ta| { |
Good catch, would you like to open a PR? |
Thanks for the kind suggestion, but no - for political reasons: Github Terms of Service arguably contains a special licensing clause which is not problematic for liberally licensed code like this project but effectively weakens stronger copyleft licensed code. I therefore never push code to Github. I already shared the code change as a patch. Please tell me if helpful to you that I provide it as a git branch that you can clone and merge. I fully understand if you have no interest in playing along with my policital game, though. |
Anyone else feel like fixing this? I notice that a new release went out, without this getting fixed :-( |
One test requires feature tls12, or it fails like this:
The text was updated successfully, but these errors were encountered: