child-delete: Reply as usual when concurrently rekeying the IKE_SA

As per RFC 7296, 2.25.2 (what we did before was the behavior described
in RFC 4718).

diff --git a/src/libcharon/sa/ikev2/tasks/child_delete.c b/src/libcharon/sa/ikev2/tasks/child_delete.c
index b79ccf3749ff9e78292429ecfbf5224a7ed037b8..6fa8836acf6282c598cb2af6e26d9dc7713decb2 100644 (file)
--- a/src/libcharon/sa/ikev2/tasks/child_delete.c
+++ b/src/libcharon/sa/ikev2/tasks/child_delete.c
@@ -382,11 +382,7 @@ METHOD(task_t, process_r, status_t,
 METHOD(task_t, build_r, status_t,
        private_child_delete_t *this, message_t *message)
 {
-       /* if we are rekeying, we send an empty informational */
-       if (this->ike_sa->get_state(this->ike_sa) != IKE_REKEYING)
-       {
-               build_payloads(this, message);
-       }
+       build_payloads(this, message);
        DBG1(DBG_IKE, "CHILD_SA closed");
        return destroy_and_reestablish(this);
 }