Skip to main content

Module tls

Module tls 

Available on crate features quic and std only.
Expand description

TLS for QUIC: how a connection’s identity and application protocol are configured.

The configuration itself is the common Rama TLS client and server configuration; this module carries only what QUIC adds to it. Inject a configuration provider explicitly, or use the convenience constructors to select the feature-default provider.

Modules§

provider
Interfaces for supplying a QUIC TLS 1.3 implementation.

Structs§

BoringTlsProviderboring
BoringSSL QUIC configuration factory.
ClientConfigCache
Reuse native TLS configuration and session state when opening QUIC connections.
NoInitialCipherSuite
The QUIC initial cipher suite, AES-128-GCM-SHA256, is unavailable or invalid.
RustlsTlsProviderrustls and (aws-lc or ring)
Rustls QUIC configuration factory with an explicitly supplied cryptographic provider.
TlsOptions
QUIC requirements applied to the common Rama TLS configuration.

Enums§

ClientHandshake
Session offer for a new TLS connection, independent of ticket retention.
ClientSessionPolicy
Client TLS ticket policy, independent of transport connection pooling.
TlsConfigError

Traits§

QuicClientConfigProvider
Build QUIC TLS configurations from Rama settings using a fixed provider.
QuicServerConfigProvider
Build server configurations without requiring client-policy support.

Functions§

default_server_tls_provider
Select the feature-default server configuration provider.
default_tls_provider
Select the feature-default configuration provider once when constructing a connector. Rustls with an enabled cryptographic implementation is preferred, then BoringSSL.