New commits:
commit 6ef3f1f06118d21482d8aaf282e3e73db16152ee
Author: Andrew Cagney <[email protected]>
Date: Thu Feb 14 18:06:29 2019 -0500
ikev2: don't segv when, while expiring a CHILD SA, the parent is missing
Seems to happen because the CHILD SA failed to establish, and started
replacing simultaneous to, or perhaps triggering, the IKE SA to also
trying to replace. Or is that the other way around?
Would a sequence like:
- generate create events for all existing child connections
- wipe out the entire family
be safer? Currently this, and children all seem to overlap leading to
fights like the above.
_______________________________________________
Swan-commit mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-commit
