Module seeds 

Implementation of special traces. Each may represent a special TLS execution like a full handshake or an execution which crashes OpenSSL.

Functions

_seed_client_attacker12

_seed_client_attacker_full

Seed which contains the whole transcript in the tree. This is rather huge >300 symbols

_seed_client_attacker_full_precomputation

_seed_server_attacker12

create_corpus

decrypt_handshake_from_claims 🔒

seed_client_attacker

seed_client_attacker12

seed_client_attacker_auth

seed_client_attacker_full

seed_client_attacker_full_precomputation

seed_server_attacker12

seed_server_attacker_full

seed_server_attacker_full_coalesced

seed_server_attacker_with_hello_retry_request

This seed sends a HelloRetryRequest message asking the TLS client to use P384 curves as keyshare and compute a correct transcript for the whole handshake The differences with seed_server_attacker_full are the addition of a round trip (server sends HRR to the client and the client sends second client hello) and the computation of the transcript following the HRR according to RFC 8446 section 4.4.1

seed_session_resumption_dhe

seed_session_resumption_dhe_full

Seed which contains the whole transcript in the tree. This is rather huge 10k symbols. It grows exponentially.

seed_session_resumption_ke

seed_successful

seed_successful12

seed_successful12_forward

This seed performs a TLS 1.2 handshake between a client and a server by only forwarding messages between the agents

seed_successful12_with_tickets

seed_successful_client_auth

seed_successful_mitm

Seed which triggers a MITM attack. It changes the cipher suite. This should fail.

seed_successful_with_ccs

seed_successful_with_tickets