On Oct 1, 2024, at 8:38 AM, Kaushal Shriyan <kaushalshri...@gmail.com> wrote:
> Thanks, Michael, for the quick response. Is there a way to capture and
> analyze *HTTPS* traffic since the data is encrypted?
Maybe, *if* you can get the necessary information; see
https://wiki.wireshark.org/TLS#tls-decryption
As it notes:
"The key log file is generally recommended since it works in all cases,
*but requires the continuous ability to export the secrets from either the
client or server application*." - emphasis mine; that's what Michael was
referring to when he said
You'll have to modify the application.
Some TLS libraries have options to dump things.
Otherwise, as Michael noted, no - the "S" in "TLS" stands for "security" (and
the first "S" in "SSL" stands for "secure"), and that's "security" as in
"preventing people from capturing your traffic and reading it".
_______________________________________________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
