3 ms·
My biggest problem with Wireshark is that it can't do anything with HTTPS traffic - which is most of the traffic I'd be interested in. I understand that's kind
by torginus 3y ago
My biggest problem with Wireshark is that it can't do anything with HTTPS traffic - which is most of the traffic I'd be interested in. I understand that's kind of the point of HTTPS, and a MITM proxy with cert replacement is somewhat out of the scope of Wireshark, it still limits the usefulness of the program.
- dv35z 3y agoCheck out Charles Proxy for mac. It’s great.
- pl4nty 3y agoit can, just not as easily as MITM proxies: https://wiki.wireshark.org/TLS https://wiki.wireshark.org/TLS
- kalmi10 3y agoThis method is really simple for Chrome, Firefox and other OpenSSL apps: https://wiki.wireshark.org/TLS#using-the-pre-master-secret https://wiki.wireshark.org/TLS#using-the-pre-master-secret You set an environment variable to instruct the app the write a file that Wireshark can use to decrypt its traffic, and change a setting in Wireshark to use that file, and that's it. You will even be able to see decrypted WebRTC traffic.