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

no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point #286

Open
Jonathan-Landeed opened this issue Aug 22, 2024 · 3 comments
Labels
question Further information is requested

Comments

@Jonathan-Landeed
Copy link

Related to snapview/tokio-tungstenite#336

I solved it by adding rustls = ">=0.23.x" to my Cargo.toml and let _ = rustls::crypto::aws_lc_rs::default_provider().install_default(); before calling slack morphism stuff, but that doesn't seem ideal.

@abdolence
Copy link
Owner

Hey, thanks for letting me know there are some issues.
I've removed my Cargo.lock to verify it with the latest builds (rustls v0.27.2 there) and It seems working with socket_mode example without changing anything. I would guess it is related to some specific features configuration in your app?

@abdolence abdolence added the question Further information is requested label Aug 23, 2024
@Jonathan-Landeed
Copy link
Author

I think it might be when tonic v0.12.1 enables the ring feature, but I'm a bit over my head on this.

I also have multiple versions of rustls installed because aws-smithy-runtime is still on rustls v0.21.12, but that shouldn't matter.

@jiangxiaoqiang
Copy link

add this code to fixed this:

rustls::crypto::ring::default_provider().install_default().expect("Failed to install rustls crypto provider");

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

No branches or pull requests

3 participants