Skip to content
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

Feature tokio-rustls-tls requires native-tls? #396

Closed
emmiegit opened this issue Jun 28, 2024 · 8 comments
Closed

Feature tokio-rustls-tls requires native-tls? #396

emmiegit opened this issue Jun 28, 2024 · 8 comments
Assignees
Labels

Comments

@emmiegit
Copy link

emmiegit commented Jun 28, 2024

Describe the bug
I'm looking at feature flag definition in Cargo.toml and the dependencies in Cargo.lock, and I noticed that the tokio-rustls-tls feature depends on native-tls, rather than using rustls. This would explain build issues I am facing due to the compilation trying to look for an openssl which isn't there.

I am noticing that the with-tokio feature in the flag list requires tokio-native-tls, native-tls, etc., whereas previously with-tokio only required ["reqwest", "tokio", "tokio/fs", "tokio-stream"]. This seems to preclude any possibility of using Tokio with rustls, despite what the feature flag list would suggest.

See 0.32.3's Cargo.toml compared to 0.34.0's.

Why does using Tokio require native TLS? Is there a way I can use only rustls instead alongside Tokio?

Environment

  • Rust version: 1.79.0
  • lib version 0.34.0

Additional context
This issue occurred when trying to upgrade to 0.34.0. See scpwiki/wikijump#1962.

@qdrs
Copy link

qdrs commented Jun 28, 2024

This is already fixed in v0.35.0-alpha.1

@LockedThread
Copy link

What is the release timeline looking like?

@emmiegit
Copy link
Author

emmiegit commented Aug 3, 2024

Is it possible to make a new full release now with this fix, and then add any other pending changes to the next full release? In case the release is being held back by some other work going on.

@LockedThread
Copy link

Is it possible to make a new full release now with this fix, and then add any other pending changes to the next full release? In case the release is being held back by some other work going on.

I second this, this is a very crucial update.

@emmiegit
Copy link
Author

Following up again here, what is required for rust-s3 to be ready for a non-alpha release containing the dependency fix here?

@durch
Copy link
Owner

durch commented Aug 31, 2024

@emmiegit, published version 0.35.0

@durch durch closed this as completed Aug 31, 2024
@emmiegit
Copy link
Author

emmiegit commented Sep 1, 2024

Thank you for your help!

@emmiegit
Copy link
Author

emmiegit commented Sep 1, 2024

Okay -- I thought I was mistaken but it seems I was not. I left a comment here: #395 (comment), basically it was working fine with cargo check (which doesn't do linking) but I was realizing that the default features were including native-tls and causing linking to fail due to lack of openssl, where I am supposed to be using rustls instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants