draft-ietf-tls-keylogfile is now RFC 9850

We have one mismatch that I can see, but I've filed crbug.com/535328567
for that.

Change-Id: I1a5d1f2d2331ed1f7ec7dea475cc4467c3d80697
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/98867
Reviewed-by: Adam Langley <agl@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
This commit is contained in:
David Benjamin
2026-07-16 01:50:53 +02:00
committed by boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com
parent 0934f4a1f9
commit 900fd15551
+1 -2
View File
@@ -5135,8 +5135,7 @@ OPENSSL_EXPORT void SSL_set_msg_callback_arg(SSL *ssl, void *arg);
// should log `line` followed by a newline, synchronizing with any concurrent
// access to the log.
//
// The format is described in
// https://www.ietf.org/archive/id/draft-ietf-tls-keylogfile-01.html
// The format is described in RFC 9850.
//
// WARNING: The data in `line` allows an attacker to break security properties
// of the TLS protocol, including confidentiality, integrity, and forward