The Mozilla developer documentation link for the NSS key log format
has been broken since early 2022. Update the documentation to point
to the IETF TLS working group draft which is currently in the RFC
publication queue.
Fixes #63331
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Change-Id: I1a87cca839e503790170a6f3a48bef3b4c6bd624
Reviewed-on: https://go-review.googlesource.com/c/go/+/741444
Reviewed-by: Daniel McCarney <daniel@binaryparadox.net>
Auto-Submit: Sean Liao <sean@liao.dev>
Reviewed-by: Roland Shoemaker <roland@golang.org>
Reviewed-by: Michael Pratt <mpratt@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Sean Liao <sean@liao.dev>
Auto-Submit: Michael Pratt <mpratt@google.com>
// KeyLogWriter optionally specifies a destination for TLS master secrets
// in NSS key log format that can be used to allow external programs
// such as Wireshark to decrypt TLS connections.
- // See https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format.
+ // See https://datatracker.ietf.org/doc/draft-ietf-tls-keylogfile/.
// Use of KeyLogWriter compromises security and should only be
// used for debugging.
KeyLogWriter io.Writer