1$OpenBSD: BUGS,v 1.15 2006/06/02 19:35:55 hshoexer Exp $ 2$EOM: BUGS,v 1.38 2000/02/18 08:47:35 niklas Exp $ 3 4Until we have a bug-tracking system setup, we might just add bugs to this 5file: 6------------------------------------------------------------------------------ 7* message_drop frees the message, this is sometimes wrong and can cause 8 duplicate frees, for example when a proposal does not get chosen. [fixed] 9 10* Notifications should be their own exchanges, otherwise the IV gets 11 disturbed. [fixed] 12 13* We need a death timeout on half-ready SAs just like exchanges. At the 14 moment we leak SAs. 15 16* When we establish a phase 2 exchange we seem to get the wrong IV set, 17 according to SSH's logs. [fixed] 18 19* If a phase 1 SA negotiation terminates with a cause that is to be sent in 20 a NOTIFY to the peer, we get multiple free calls on the cleanup of the 21 informational exchange. [fixed] 22 23* IKE mandates that a HASH should be added to informational exchanges in 24 phase 2. [fixed] 25 26* Message_send requires an exchange to exist, and potentially it tries to 27 encrypt a message multiple times when retransmitting. [fixed] 28 29* Multiple protocol proposals seems to fail. [fixed] 30 31* The initiator fails to match the responders choice of protocol suite with 32 the correct one of its own when several are offered. [fixed] 33 34* Duplicate specified sections is not detected. [fixed] 35 36* Quick mode establishments via UI using -P bind-addr gets "Address already in 37 use". 38 39* Not chosen proposals should be deleted from the protos list in the sa 40 structure. [fixed] 41 42* Setting SPIs generates "Invalid argument" errors due to one tunnel endpoint 43 being INADDR_ANY. [fixed] 44 45* ipsec_proto structs are never allocated. [fixed] 46 47* Remove SPIs of unused proposals. [fixed] 48 49* If the first proposal is turned down, the initiator gets confused. 50 51* Renegotiation after a failed phase 1 fails. 52 53* Phase 1 rekey event removal seems to be done twice. [fixed] 54 55* PF_ENCAP expirations does not find the proper phase 2 SA to remove. [fixed] 56 57* ISAKMP SA expirations should have a soft/hard timeout just like IPsec ones. 58 The soft one should put a watchdog on the SA, and start a renegotiation as 59 soon as something used the SA. Hard ones should just clean it up, no 60 renegotiation at all. [fixed] 61 62* ISAKMP SAs does not get removed after rekeying. [fixed] 63 64* On-demand PF_ENCAP SAs does not get reestablished. [fixed] 65 66* Rekeying is now done automatically on expirations, it should not. The 67 SAs should be brought up on-demand just like the first time. 68 69* Notifications regarding exchange errors seems to not have the right SPI, 70 at least not in phase 1, in NO_PROPOSAL_CHOSEN. 71 72* Outgoing informational exchanges when we use INVALID_PAYLOAD_TYPE 73 cause a DOI error. 74 75* In Linux select(2) of named pipes seems broken as they will return as 76 readable even when nothing is there after one read has succeeded. 77 78* I have seen INITIAL-CONTACT sent on the second Main Mode. 79 80* When ID mismatches occur, coredumps may follow, investigate! 81 82* ESP+AH does not work properly 83 84* Looping QM seen (due to lost sendpackets from other participant?) 85 86* Teardown from UI does not remove exchanges. 87 88* Wrong error message when policy check fails. 89 90* Retransmit of QM (packet 1) after INFO/PAYLOAD_MALFORMED was received. 91 92* SIGSEGV after sa_enter: sa added to sa list, trigged by DELETE notify (Linux) 93 94* Passive connections, undefined local&remote IDs will cause IKE peer IDs 95 to be used. 96 97* host route support in KLIPS does not work properly 98 99* When not having compiled in support for a certain crypto algorithm and 100 the config file still tells us to propose it, we segfault. 101