Expand description
§ytls-traits
Traits for ytls
Structs§
- Handshake
Complete - Marker for Handshake being complete
- Shutdown
Complete - Marker for Shutdown being complete
Enums§
Traits§
- Client
Handshake Finished Builder - Client handshake finished is provided through trait implementation
- Client
Hello Builder - Use to generate ClientHello with the Handshake builder. Provide the optional / required data to construct it.
- Client
Hello Processor - Crypto
ChaCha20 Poly1305 Processor - ChaCha20Poly1305 AEAD Processor
- Crypto
Config - Cryptography configuration is provied through implmenting this trait. Typically providers provide implementation or implementer can provide a mix of used primitives.
- Crypto
Rng - A marker trait over
RngCorefor securely unpredictable RNGs - Crypto
Sha256 Hkdf Extract Processor - HKDF (Hashing Key Derivation Function) Extract Processor
- Crypto
Sha256 Hkdf GenProcessor - HKDF Gen Processor, e.g. to Expand
- Crypto
Sha256 Hmac Processor - HMAC (Hash-based Message Authentication Code) SHA256. @At Handshake Finished
- Crypto
Sha256 Transcript Processor - Transcript processor used to hash handshakes. Typically implemented by the crypto provider.
- Crypto
Sha384 Hmac Processor - HMAC (Hash-based Message Authentication Code) SHA384. @At Handshake Finished
- Crypto
Sha384 Transcript Processor - Transcript processor used to hash handshakes. Typically implemented by the crypto provider.
- Crypto
Signer P256 Processor - ECDSA Signature Processor secp256p1
- Crypto
X25519 Processor - X25519 processor used to calculate the shared secret with the given input public key and returning the shared secret.
- CtxApplication
Processor - Implement to process application data part
- CtxHandshake
Processor - Implement to process handshaking part
- Encrypted
Extensions Builder - Encrypted Extensions are provided through trait implementation if any
- Handshake
Builder - Non-typed Handshake Builder with raw data inputs.
This is implemented by the [
ytls_record::Record] where as the required inputs are through the client/server contextes. - Secret
Store - up old secrets when not needed anymore beyond their purpose. When context upgrades we need to store/load generated ap secrets
- Server
ApRecord Processor - Server
Certificate Processor - Server
Certificate Verify Builder - Server certificate verification is provided through trait implementation
- Server
Certificate Verify Processor - Server
Certificates Builder - Server certificates are provided through trait implementation
- Server
Finished Processor - Server
Handshake Finished Builder - Server handshake finished is provided through trait implementation
- Server
Hello Builder - Use to generate ServerHello with the HandshakeBuilder. Provide the optional / required data to construct it.
- Server
Hello Processor - Server
Record Processor - Server
Wrapped Record Processor - Tls13
KeySchedule ApSha256 - TLS1.3 “Main” Key Schedule for Application Traffic post-handshake.
- Tls13
KeySchedule Derived Sha256 - TLS1.3 “derived” Key Schedule
- Tls13
KeySchedule Handshake Sha256 - TLS1.3 “handshake” Key Schedule
- Tls13
KeySchedule Init - Initialize TLS1.3 Key Schedule
- TlsLeft
In - TLS State Machine Left (Ciphertext) or “Network” I/O ingress side
- TlsLeft
Out - TLS State Machine Left (Ciphertext) or “Network” I/O egress side
- TlsRight
- TLS State Machine Right (Cleartext) or “Application” I/O side
- Wrapped
Application Builder - Wrapped Application data within Application context builder
- Wrapped
Handshake Builder - Same except non-wrapped but where we wrap the record into TLS 1.2 Application Data layer, typically encrypted when written to wire.