aabb31871d
racoon uses a wrong IPsec-SA handle that is for other peer in case it receives a ISAKMP message for IPsec-SA that has the same message-id as the message-id that is received before. racoon uses message-id to find the handle of IPsec-SA. The message-id is a unique number for each peer, but different peers may use the same value. Different Windows Vista or Windows 7 peers seem to use the same message-id. racoon can handle the first Windows's Phase-2, but it cannot handle the second Windows. Because racoon misunderstands the message for the second Windows as the message for the first Windows. >Category: bin >Synopsis: racoon uses a wrong IPsec-SA that is for different peer >Confidential: no >Severity: serious >Priority: medium >Responsible: bin-bug-people >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Nov 22 18:25:00 +0000 2009 >Originator: yasuoka@iij.ad.jp |
||
|---|---|---|
| .. | ||
| dist | ||
| external | ||
| Makefile.openssl | ||
| TODO | ||