# TLS 1.3 traffic keys rotated mid-connection

TLS 1.3 traffic keys rotated mid-connection: the server sends a KeyUpdate between two responses on one connection.

Its keys file is byte-identical to tls13-minimal's, on purpose: both are built from the same synthetic handshake secrets, and the keys after the KeyUpdate are derived from those (RFC 8446 section 7.2), so the file needs no more lines.

- What success looks like: Both requests and both responses decode, including the response sent under the new keys.
- What error it exposes: A decoder that keeps using the old traffic secret after a KeyUpdate.
- Kind: synthetic (generated, no real traffic)
- Protocols: HTTP/1.1, TLS 1.3
- Keys: embedded in tls13-key-update.pcapng as a Decryption Secrets Block, and in tls13-key-update.keys.txt as an NSS key log
- Expected decoded output: tls13-key-update.expected.json (JSON), confirmed by an independent decoder before publication
- Regenerate: cargo run -p synthetic-pcap --example tls13_h1_gen -- --variant keyupdate --name tls13_keyupdate --out <dir>
- Licence: Creative Commons Attribution 4.0 International (CC BY 4.0), for the released capture and expected-output files only. Attribution: Shorenet Ltd.
- Download all: tls13-key-update.zip holds these files, the licence text (LICENCE.txt) and their SHA-256 (SHA256SUMS)

## Files

- tls13-key-update.pcapng
- tls13-key-update.keys.txt
- tls13-key-update.expected.json
- tls13-key-update.md