Tobias Brunner ecba84a06b child-delete: Don't send delete for expired CHILD_SAs that were already rekeyed ... The peer might not have seen the CREATE_CHILD_SA response yet, receiving a DELETE for the SA could then trigger it to abort the rekeying, causing the deletion of the newly established SA (it can't know whether the DELETE was sent due to an expire or because the user manually deleted it). We just treat this SA as if we received a DELETE for it. This is not an ideal situation anyway, as it causes some traffic to get dropped, so it should usually be avoided by setting appropriate soft and hard limits. References #2815.		2018-11-22 11:31:53 +01:00
..
authenticators	pubkey-authenticator: Append RSAPSS salt length to debug output	2018-10-26 09:55:07 +02:00
tasks	child-delete: Don't send delete for expired CHILD_SAs that were already rekeyed	2018-11-22 11:31:53 +01:00
connect_manager.c	Unify format of HSR copyright statements	2018-05-23 16:32:53 +02:00
connect_manager.h	Unify format of HSR copyright statements	2018-05-23 16:32:53 +02:00
keymat_v2.c	keymat_v2: Add support for PPKs	2018-09-10 18:03:01 +02:00
keymat_v2.h	keymat_v2: Add support for PPKs	2018-09-10 18:03:01 +02:00
mediation_manager.c	Unify format of HSR copyright statements	2018-05-23 16:32:53 +02:00
mediation_manager.h	Unify format of HSR copyright statements	2018-05-23 16:32:53 +02:00
task_manager_v2.c	task-manager-v2: Reject requests for incomplete IKE_SAs as initiator	2018-10-26 11:22:08 +02:00
task_manager_v2.h	Use separate Doxygen groups for IKEv1 and IKEv2 entities (authenticators, tasks etc.).	2012-05-18 10:04:08 +02:00