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

ikev2: keep the CHILD_SA we delete as initiator in the list to destroy

Browse Source 
If the responder not correctly send the correct protocol or SPI in the delete
response, we should remove the CHILD_SA regardless.
This commit is contained in:
Martin Willi
2013-06-25 14:03:51 +02:00
parent 72631301eb
commit a650242643
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/libcharon/sa/ikev2/tasks/child_delete.c
+5 -6
View File
@@ -177,8 +177,11 @@ static void process_payloads(private_child_delete_t *this, message_t *message)
default: default:
break; break;
} }
if (this->child_sas->find_first(this->child_sas, NULL,
this->child_sas->insert_last(this->child_sas, child_sa); (void**)&child_sa) != SUCCESS)
{
this->child_sas->insert_last(this->child_sas, child_sa);
}
} }
spis->destroy(spis); spis->destroy(spis);
} }
@@ -310,10 +313,6 @@ METHOD(task_t, build_i, status_t,
METHOD(task_t, process_i, status_t, METHOD(task_t, process_i, status_t,
private_child_delete_t *this, message_t *message) private_child_delete_t *this, message_t *message)
{ {
/* flush the list before adding new SAs */
this->child_sas->destroy(this->child_sas);
this->child_sas = linked_list_create();
process_payloads(this, message); process_payloads(this, message);
DBG1(DBG_IKE, "CHILD_SA closed"); DBG1(DBG_IKE, "CHILD_SA closed");
return destroy_and_reestablish(this); return destroy_and_reestablish(this);