| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | ikev2: Ignore IKEV2_MESSAGE_ID_SYNC notifies if extension is disabled | Tobias Brunner | 2017-02-08 | 1 | -0/+7 |
| | | | | | | | | | | | If this is the first message by the peer, i.e. we expect MID 0, the message is not pre-processed in the task manager so we ignore it in the task. We also make sure to ignore such messages if the extension is disabled and the peer already sent us one INFORMATIONAL, e.g. a DPD (we'd otherwise consider the message with MID 0 as a retransmit). | ||||
| * | ikev2: Don't increase expected MID after handling MID sync message | Tobias Brunner | 2017-02-08 | 1 | -3/+1 |
| | | | | | | | | | If the responder never sent a message the expected MID is 0. While the sent MID (M1) SHOULD be increased beyond the known value, it's not necessarily the case. Since M2 - 1 would then equal UINT_MAX setting that MID would get ignored and while we'd return 0 in the notify we'd actually expect 1 afterwards. | ||||
| * | ikev2: Add task to handle IKEV2_MESSAGE_ID_SYNC notifies as responder | Tobias Brunner | 2017-02-08 | 1 | -0/+259 |
 |
index : tteras/strongswan | |
| tteras' strongSwan tree | gitolite |
| aboutsummaryrefslogtreecommitdiffstats |