Open Hub
Open Hub

 Settings |  Report Duplicate

10
I Use This!
Inactive

News

Analyzed about 1 hour ago. based on code collected about 1 hour ago.
when IKEv1 notices that the remote end has sent a IKEv2 VID and we
Posted over 17 years ago by Michael Richardson <[email protected]>
when IKEv1 notices that the remote end has sent a IKEv2 VID and we
added test case for recover from bid-down attack.
Posted over 17 years ago by Michael Richardson <[email protected]>
added test case for recover from bid-down attack.
In testing of ikev2-03, it was noticed that the IPsec SA (CHILD/Phase2)
Posted over 17 years ago by Michael Richardson <[email protected]>
In testing of ikev2-03, it was noticed that the IPsec SA (CHILD/Phase2)
rekey times are now set to proper defaults.
Posted over 17 years ago by Michael Richardson <[email protected]>
rekey times are now set to proper defaults.
(no commit message)
Posted over 17 years ago by Antony Antony <[email protected]>
(no commit message)
use a vendor ID for the flag that IKEv2 is supported rather than a
Posted over 17 years ago by Michael Richardson <[email protected]>
use a vendor ID for the flag that IKEv2 is supported rather than a
switched to using an VendorID for IKEV2 notification, as this works with
Posted over 17 years ago by Michael Richardson <[email protected]>
switched to using an VendorID for IKEV2 notification, as this works with
added notification of capability to do IKEv2
Posted over 17 years ago by Michael Richardson <[email protected]>
added notification of capability to do IKEv2
test case for notification by responder that it can in fact do IKEv2.
Posted over 17 years ago by Michael Richardson <[email protected]>
test case for notification by responder that it can in fact do IKEv2.
removed errant ikev1->ikev2 retry code.
Posted over 17 years ago by Michael Richardson <[email protected]>
removed errant ikev1->ikev2 retry code.