https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16517
Peter Wu <pe...@lekensteyn.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pe...@lekensteyn.nl
--- Comment #11 from Peter Wu <pe...@lekensteyn.nl> ---
I disagree with the title "Environment variables should be documented" where
"environment variables" are not from Wireshark itself. This report seems like a
request to add documentation for setting up TLS decryption. That is not what
the title says.
In that case, I believe that the existing documentation (the wiki and the many
references on that page) is sufficient.
SSLKEYLOGFILE is one variable to obtain secrets from some applications, but it
is not the only one. The name is a convention that started from the NSS
library as used by Firefox. Although some applications (Chromium, curl,
recently some configurations of Python 3.8, ...) support this environment
variables, not all of them do. Some applications such as "openssl s_client",
"openssl s_server", node (Node.JS) and chrome expose a command-line option to
configure the keylog output file. There are also TLS terminator appliances that
provide these secrets.
The User's Guide is mostly a document describing the user interface of
Wireshark. It has little use-case driven documentation, and describing external
applications is probably out of scope.
Who would benefit from a description in the User's Guide while we already have
excellent descriptions, presentations, and videos elsewhere?
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
