denozord/strongswan-ext
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Allow ID_PROT/AGGRESSIVE messages for established IKE_SAs if they contain fragments

Browse Source 
Other implementations send fragments always in an initial message type
even for transaction or quick mode exchanges.
This commit is contained in:
Tobias Brunner
2012-12-24 12:29:27 +01:00
parent 8fc8383439
commit b816037739
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/libcharon/sa/ike_sa.c
+2 -1
View File
@@ -1232,7 +1232,8 @@ METHOD(ike_sa_t, process_message, status_t,
case IKE_SA_INIT: case IKE_SA_INIT:
case IKE_AUTH: case IKE_AUTH:
if (this->state != IKE_CREATED && if (this->state != IKE_CREATED &&
this->state != IKE_CONNECTING) this->state != IKE_CONNECTING &&
message->get_first_payload_type(message) != FRAGMENT_V1)
{ {
DBG1(DBG_IKE, "ignoring %N in established IKE_SA state", DBG1(DBG_IKE, "ignoring %N in established IKE_SA state",
exchange_type_names, message->get_exchange_type(message)); exchange_type_names, message->get_exchange_type(message));