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
..
suites	child-delete: Don't send delete for expired CHILD_SAs that were already rekeyed	2018-11-22 11:31:53 +01:00
utils	unit-tests: Add mock implementation of kernel_net_t	2018-06-22 09:20:30 +02:00
.gitignore	libcharon: Add exchange_tests to .gitignore	2016-07-25 14:01:26 +02:00
Makefile.am	unit-tests: Add tests for peer_cfg_t::replace_child_cfgs()	2018-09-10 17:45:23 +02:00
exchange_tests.c	unit-tests: Add separate test runner to test IKEv2 exchanges	2016-06-17 18:48:01 +02:00
exchange_tests.h	unit-tests: Add test cases for MID sync exchanges	2017-02-08 15:11:00 +01:00
libcharon_tests.c	daemon: Use separate method to set default loggers	2017-01-25 14:58:09 +01:00
libcharon_tests.h	unit-tests: Add tests for peer_cfg_t::replace_child_cfgs()	2018-09-10 17:45:23 +02:00