Re: [Wireshark-dev] re-load IKEv2 / ESP UAT during wireshark gui runtime

2021-08-19 Thread Martin Mathieson via Wireshark-dev
I have nothing against a text keylog file approach, but FWIW with ESP UAT (or the run-time function I mentioned), you can configure the key in hex prefixed with 0x. Martin On Thu, Aug 19, 2021 at 6:37 PM Nicolás Alvarez wrote: > El jue, 19 de ago. de 2021 a la(s) 08:30, Harald Welte >

Re: [Wireshark-dev] re-load IKEv2 / ESP UAT during wireshark gui runtime

2021-08-19 Thread Nicolás Alvarez
El jue, 19 de ago. de 2021 a la(s) 08:30, Harald Welte (lafo...@gnumonks.org) escribió: > > Sorry if this has been covered before, but I could only find several > locations online where the question has been asked, but no response anywhere: > > Is there already a mechanism by which a running

Re: [Wireshark-dev] re-load IKEv2 / ESP UAT during wireshark gui runtime

2021-08-19 Thread Martin Mathieson via Wireshark-dev
Hi Harald, I realise this may not be convenient for you, but what I have done a couple of times is to have a private dissector parse logging frames in the same capture that contain info about new SAs being created. With all of the relevant information in hand, the dissector then calls

[Wireshark-dev] re-load IKEv2 / ESP UAT during wireshark gui runtime

2021-08-19 Thread Harald Welte
Sorry if this has been covered before, but I could only find several locations online where the question has been asked, but no response anywhere: Is there already a mechanism by which a running wireshark can be triggered to re-load UAT tables at runtime, in my specific use case those for IKEv2