From fbcc8fd6e814fbc1394764a34bbefee503b98165 Mon Sep 17 00:00:00 2001 From: Boquan Fang Date: Tue, 4 Mar 2025 10:02:36 -0800 Subject: [PATCH] fix: typo for debugging book (#2509) * fix: typo for debugging book * Update docs/user-guide/debugging-pcap.md Co-authored-by: Cameron Bytheway --------- Co-authored-by: Boquan Fang Co-authored-by: Cameron Bytheway --- docs/user-guide/debugging-pcap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/debugging-pcap.md b/docs/user-guide/debugging-pcap.md index 8d3c8b7ae..4049aa2bc 100644 --- a/docs/user-guide/debugging-pcap.md +++ b/docs/user-guide/debugging-pcap.md @@ -7,7 +7,7 @@ A packet capture allows for inspecting the contents of every packet transmitted Since QUIC is an encrypted transport protocol, the payload of each packet is not readable in a standard packet capture. `s2n-quic` supports exporting the TLS session keys used by each QUIC connection so that the packet capture may be decrypted. Both the `s2n-tls` and `rustls` TLS providers support key logging through their associated builders: ```rust -let tls = s2n_quic::provider::tls::default::Serverhell::builder() +let tls = s2n_quic::provider::tls::default::Server::builder() .with_certificate(CERT_PEM, KEY_PEM)? .with_key_logging()? // enables key logging .build()?;