This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| network_stuff:wireshark [2023/01/27 18:26] – jotasandoku | network_stuff:wireshark [2025/07/10 21:21] (current) – jotasandoku | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| **__WIRESHARK NOTES__**\\ | **__WIRESHARK NOTES__**\\ | ||
| - | [[https:// | + | [[https:// |
| This is to caprutue and show in wireshark live traffic. Running on a linux based router like openwrt: | This is to caprutue and show in wireshark live traffic. Running on a linux based router like openwrt: | ||
| Line 35: | Line 35: | ||
| __Analyse__\\ | __Analyse__\\ | ||
| - | FIRST THING determine in which end of the conversation we are capturing the packets << | + | FIRST THING determine in which end of the conversation we are capturing the packets << |
| \\ | \\ | ||
| Line 141: | Line 141: | ||
| dumpcap -i eth0 -b duration: | dumpcap -i eth0 -b duration: | ||
| | | ||
| + | |||
| + | ---- | ||
| + | *** DECRYPT A TLS SESSION *** | ||
| + | Several applications honor the SSLKEYLOGFILE environment variable, which allows you to log the TLS session key, and which e.g., Wireshark can read to then decrypt the TLS packets.1 To use it, simply export SSLKEYLOGFILE=/ | ||
| + | |||
| + | \\ | ||
| + | |||
| + | both Chrome and Firefox honor the SSLKEYLOGFILE environment variable, making dissecting packets nice and easy. | ||
| + | |||
| + | $ export SSLKEYLOGFILE=/ | ||
| + | $ / | ||