https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16517
Christopher Maynard <christopher.mayn...@igt.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #12 from Christopher Maynard <christopher.mayn...@igt.com> ---
(In reply to Peter Wu from comment #11)
> This report seems like a request to add documentation for setting up TLS
> decryption. That is not what the title says.
I didn't intend the mentioning of SSLKEYLOGFILE to take over the primary
discussion on this bug report, nor did I intend for it being "documented" in
the User Guide as turning into a complete "How To" on setting up TLS
decryption. As mentioned in previous comments, some wiki content has recently
been moved to the User Guide, notably some Lua information. But there is
currently no mention in the User Guide at all that TLS decryption is even
possible in some cases (firefox, chrome, curl, possibly others). The thought
was to merely mention the basic general steps involved, e.g., "It's possible
for Wireshark to decrypt HTTPS traffic with browsers that support exporting of
a key log file, generally enabled by setting the SSLKEYLOGFILE environment
variable. For more information on how to achieve this, refer to ... <whatever
links we want to supply here including but not limited to
https://wiki.wireshark.org/TLS>".
On a side note, I believe Wireshark, being the de facto packet capture
standard, is in a rather unique position to possibly help influence other
software, By specifically mentioning the SSLKEYLOGFILE mechanism for enabling
the exporting of the keys, perhaps that would help encourage software that
doesn't currently support this feature to add it using the same familiar
method, especially if more Wireshark users are aware of it and begin inquiring
about it. Here, I'll just mention the mosquitto project as one example and
refer you to https://github.com/eclipse/mosquitto/issues/632 if you're curious,
but this is by no means isn't just about mosquitto.
> Who would benefit from a description in the User's Guide while we already
> have excellent descriptions, presentations, and videos elsewhere?
As for the other Wireshark-specific environment variables, I think they're also
worth mentioning in the User Guide because I don't presume to know the needs of
all users, and I think providing the information only makes the tool more
useful to more people. As for having excellent descriptions, presentations and
videos elsewhere, I don't disagree with you there and the changes proposed here
were never meant to replace them.
Well, as far as I can tell, the changes I've proposed are not at all
well-received, and since I seem to be the only one who thinks mentioning the
environment variables or anything about the SSLKEYLOGFILE in the User Guide
would be useful for Wireshark users, I'll just go ahead and close the bug. The
consensus seems to be that the current documentation is sufficient and that
this content doesn't belong in the User Guide, so there's no point in keeping
the bug open.
--
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
