CryptoProvider error #8

Open
opened 2024-10-05 03:04:46 +13:00 by Dolu89 · 3 comments
Dolu89 commented 2024-10-05 03:04:46 +13:00 (Migrated from github.com)

Hey
I'm on macos m1 arch, I don't know if it's related, but I got this error when trying to launch the program

*** CONNECTING ***
thread 'main' panicked at /Users/dolu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.23.12/src/crypto/mod.rs:259:14:
no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

I fixed the error by doing this https://github.com/rustls/rustls/issues/1938#issuecomment-2099920256

Hey I'm on macos m1 arch, I don't know if it's related, but I got this error when trying to launch the program ``` *** CONNECTING *** thread 'main' panicked at /Users/dolu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.23.12/src/crypto/mod.rs:259:14: no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point note: run with RUST_BACKTRACE=1 environment variable to display a backtrace ``` I fixed the error by doing this https://github.com/rustls/rustls/issues/1938#issuecomment-2099920256
mikedilger commented 2024-10-05 08:01:48 +13:00 (Migrated from github.com)

woah. Ok I'll look into this later. Glad you found a fix for yourself.

woah. Ok I'll look into this later. Glad you found a fix for yourself.
mikedilger commented 2024-10-08 10:00:31 +13:00 (Migrated from github.com)

This is a bit weird since we don't directly depend on rustls. We depend on other crates which themselves depend on rustls. We shouldn't have to do this, and if it has to be done it should be done by the upstream crates (reqwest, tokio-tungstenite)

https://github.com/seanmonstar/reqwest/issues/2423

This is where tungstenite clobbered the NECESSARY rustls choice between aws-lc-rs and ring by clobbering both features:

github.com/snapview/tungstenite-rs@0e25483753

This is a bit weird since we don't directly depend on rustls. We depend on other crates which themselves depend on rustls. We shouldn't have to do this, and if it has to be done it should be done by the upstream crates (reqwest, tokio-tungstenite) https://github.com/seanmonstar/reqwest/issues/2423 This is where tungstenite clobbered the NECESSARY rustls choice between `aws-lc-rs` and `ring` by clobbering both features: https://github.com/snapview/tungstenite-rs/commit/0e25483753f76b542a98052078149490ea12e69e
mikedilger commented 2025-02-03 10:41:22 +13:00 (Migrated from github.com)

I've added the hack at that comment. I hope it works for everyone.

I've added the hack at that comment. I hope it works for everyone.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nostr/relay-tester#8
No description provided.