Fix: use ring as a crypto provider instead of aws_lc (#15812)

This commit is contained in:
Piepmatz
2025-05-24 15:01:29 +02:00
committed by GitHub
parent 6bf955a5a5
commit ea97229688
4 changed files with 8 additions and 93 deletions

View File

@ -91,7 +91,7 @@ rusqlite = { workspace = true, features = [
"backup",
"chrono",
], optional = true }
rustls = { workspace = true, optional = true }
rustls = { workspace = true, optional = true, features = ["ring"] }
rustls-native-certs = { workspace = true, optional = true }
rmp = { workspace = true }
scopeguard = { workspace = true }

View File

@ -42,7 +42,7 @@ use ureq::TlsConnector;
/// use nu_command::tls::CRYPTO_PROVIDER;
///
/// // Call once at startup
/// CRYPTO_PROVIDER.set(|| Ok(rustls::crypto::aws_lc_rs::default_provider()));
/// CRYPTO_PROVIDER.set(|| Ok(rustls::crypto::ring::default_provider()));
/// ```
///
/// Only the first successful call takes effect. Later calls do nothing and return `false`.
@ -99,7 +99,7 @@ impl NuCryptoProvider {
/// If it fails, use [`set`](Self::set) to install a custom one.
/// Returns whether the provider was stored successfully.
pub fn default(&self) -> bool {
self.set(|| Ok(rustls::crypto::aws_lc_rs::default_provider()))
self.set(|| Ok(rustls::crypto::ring::default_provider()))
}
}