acton-service 0.27.1

Production-ready Rust backend framework with type-enforced API versioning
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

//! Rustls crypto provider bootstrap.
//!
//! `rustls 0.23+` requires a process-wide default [`CryptoProvider`] to be
//! installed before `ServerConfig::builder()` or `ClientConfig::builder()` is
//! called. When more than one provider is compiled into the binary (which
//! happens routinely via transitive deps such as `quinn-proto` and
//! `jsonwebtoken`), the implicit default is ambiguous and the builder panics.
//!
//! [`ensure_default_crypto_provider`] installs the provider chosen at compile
//! time via the `crypto-aws-lc-rs` (default) or `crypto-ring` feature. It is
//! idempotent and safe to call from multiple places.
//!
//! [`CryptoProvider`]: rustls::crypto::CryptoProvider

use std::sync::Once;

static INIT: Once = Once::new();

/// Install the rustls default [`CryptoProvider`] selected at compile time.
///
/// Called automatically by [`crate::tls::load_server_config`]. Binaries that
/// drive `reqwest`, `sqlx`, or `tonic` TLS clients without going through the
/// framework's TLS listener should call this from `main` before issuing any
/// TLS request.
///
/// Idempotent: subsequent calls are no-ops.
///
/// [`CryptoProvider`]: rustls::crypto::CryptoProvider
pub fn ensure_default_crypto_provider() {
    INIT.call_once(|| {
        #[cfg(feature = "crypto-aws-lc-rs")]
        let _ = rustls::crypto::aws_lc_rs::default_provider().install_default();
        #[cfg(feature = "crypto-ring")]
        let _ = rustls::crypto::ring::default_provider().install_default();
    });
}