You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For R&D, it is very useful to look at the decrypted traffic in wireshark. One can copy+paste the various key material manually from stdout of the program to the wireshark UI, but that's very tmie consuming and inefficient.
I'm planning to create a patch that generates the esp_sa and ikev2_decryption_table lines for the related files in ~/.wireshark/
The text was updated successfully, but these errors were encountered:
I also thought doing something similar, but my main setup is using this tool in one VM, and an ePDG in another VM or in the network, so i usually do the wireshark capture directly in windows vmnet1/8 interfaces, or via trace directly in the ePDG (that already generates ununcrypted payloads).
For R&D, it is very useful to look at the decrypted traffic in wireshark. One can copy+paste the various key material manually from stdout of the program to the wireshark UI, but that's very tmie consuming and inefficient.
I'm planning to create a patch that generates the esp_sa and ikev2_decryption_table lines for the related files in ~/.wireshark/
The text was updated successfully, but these errors were encountered: