You can get the keys from strongswan debug logs. Strongswan
is having detailed debugging logs.
Check strongswan wiki for more information about logs.
Regards,
Saravanan N
On Thu, Dec 20, 2012 at 1:11 PM, jegathesh malaiyappan <
mjegakat...@gmail.com> wrote:
> Hi,
>
> How do we get the key's (SK_
Hi,
How do we get the key's (SK_e and SK_a.) used to encrypt the packets?
Thanks.
- jegathesh
On Thu, Dec 20, 2012 at 1:07 PM, SaRaVanAn
wrote:
> Hi,
> You can decrypt IKEv2 using the plugins available in Wireshark.
> Wireshark 1.8 has the provision for it.
>
> Regards,
> Saravanan N
>
> On We
Hi,
You can decrypt IKEv2 using the plugins available in Wireshark.
Wireshark 1.8 has the provision for it.
Regards,
Saravanan N
On Wed, Dec 19, 2012 at 6:24 PM, jegathesh malaiyappan <
mjegakat...@gmail.com> wrote:
> Hi,
>
> Is there any tool available to decrypt the IKE packets(IKE_AUTH,
> IN
This is useful for certain test cases. Passing the sequence number to
the callback requires a new struct that contains both the number and the
xfrm_usersa_id. The new configuration parameter is called oseq in
accordance with the kernel name, see the comment in the reset_cb
callback function for det
Hi,
Is there any tool available to decrypt the IKE packets(IKE_AUTH,
INFORMATIONAL) exchanged during negotiation?
--
By
M.Jegathesh,
___
Dev mailing list
Dev@lists.strongswan.org
https://lists.strongswan.org/mailman/listinfo/dev
Hi Volker,
> this is the resubmitted draft-ietf-ipsec-nat-t-ike-02 support patch. I
> changed everything you suggested in your review.
Excellent. I've applied it to master [1]. Thanks again for the patch.
> I'm not so sure about what you consider a non-trivial change. I hope I
> got that right
