-
Notifications
You must be signed in to change notification settings - Fork 746
Open
Description
I was looking up how to implement a custom crypto provider. It looks like it's not currently documented in a consolidated place. These are all the traits found in modules under rustls::crypto, plus some in rustls::quic. Could someone confirm whether this is the full set? Also, does each provider need to implement all of the ones not marked Optional, or is it expected that some providers would delegate to an existing default implementation for some of them?
- CryptoProvider
- ActiveKeyExchange
- SupportedKxGroup
- cipher::MessageDecrypter
- cipher::MessageEncrypter
- cipher::Tls12AeadAlgorithm
- cipher::Tls13AeadAlgorithm
- signer::Signer
- signer::SigningKey
- tls12::Prf
- hash::Hash
- hash::Context
- tls13::Hkdf
- tls13::HkdfExpander
- hmac::Hmac
- hmac::Key
Optional: QUIC
Optional: HPKE
Metadata
Metadata
Assignees
Labels
No labels