aboutsummaryrefslogtreecommitdiffstats
path: root/testing/ssh_config
diff options
context:
space:
mode:
authorTobias Brunner <tobias@strongswan.org>2017-08-29 09:06:55 +0200
committerTobias Brunner <tobias@strongswan.org>2017-09-04 11:16:00 +0200
commitc353996191dbc3ab591278917dc3d08169ed1cc2 (patch)
treead5f70bb406420b1565a3d5df60c6307b9953e69 /testing/ssh_config
parenteaedcf8c0054e9439969edfaf11e8e49df0e9c49 (diff)
downloadstrongswan-c353996191dbc3ab591278917dc3d08169ed1cc2.tar.bz2
strongswan-c353996191dbc3ab591278917dc3d08169ed1cc2.tar.xz
ike: Reset local SPI if retrying to connect in state IKE_CONNECTING
In case we send retransmits for an IKE_SA_INIT where we propose a DH group the responder will reject we might later receive delayed responses that either contain INVALID_KE_PAYLOAD notifies with the group we already use or, if we retransmitted an IKE_SA_INIT with the requested group but then had to restart again, a KE payload with a group different from the one we proposed. So far we didn't change the initiator SPI when restarting the connection, i.e. these delayed responses were processed and might have caused fatal errors due to a failed DH negotiation or because of the internal retry counter in the ike-init task. Changing the initiator SPI avoids that as we won't process the delayed responses anymore that caused this confusion.
Diffstat (limited to 'testing/ssh_config')
0 files changed, 0 insertions, 0 deletions