Traits

Traits are the ❤️ of everything

In order to provide non-monolithic de-coupling, traits are everywhere.

Builder traits

Builder traits are involved in the record generation and provides callbacks to provide data upon construction before they are pushed into the wire

You can find them here: traits/src/t_builder.rs

Cryptography traits

Found here: traits/src/t_crypto.rs

Example impl: crypto/rustcrypto

Context usage example: server/examples/listener.rs

Processor config example: crypto/rustcrypto/src/lib.rs

Validation through trait impl. validation/crypto

Context

Context is the stateful TLS context that is wound forward with data providing the protocol state machine.

Found here: traits/src/t_ctx.rs

Example impls: server/src

These are implemented in the contextes but they are de-coupled.

Input / Output

We have Left and Right sides for I/O where typically the Left is the Ciphertext Network I/O side and the right being side being the Application I/O for Cleartext.

The traits can be found here: traits/src/t_io.rs

Example naive I/O impl found here: server/examples/listener.rs

The I/O reflects how Left/Right also works in yaws.

To "hook" I/O or integration with the given I/O traits the following traits are implemented somewhere the I/O is concerned.

Keying

Traits for keys provides key / schedule operations.

Found from here: traits/src/t_keys.rs

Implemented here for TLS 1.3: keys/src/tls13_key_schedule.rs

Parsing

Found here: [traits/src/t_parser.rs]