From 110d3ed8526197bd866e02199bfeae7569d73d8d Mon Sep 17 00:00:00 2001 From: Dimitri Staessens Date: Sun, 21 Jun 2026 13:35:45 +0200 Subject: irmd: Complete bidirectional flow re-keying Extend re-key delivery beyond the locally-initiated watermark path: Handle peer-initiated re-key requests, allowing one request and one response per flow at a time. The client side wins if both ends try to re-key at the same time. Caches the peer certificate to support cert-less authenticated/signed re-keys. After a rekey, the initiator promotes first (timer) and starts sending under the new key. The responder observes the new key (peer_synced) and then the responder promotes. The responder will self-decide to use the new keys if it exhausted the older set in the case where it never sees the peer (unidirectional flow). Signed-off-by: Dimitri Staessens Signed-off-by: Sander Vrijders --- src/lib/pb/irm.proto | 1 + 1 file changed, 1 insertion(+) (limited to 'src/lib/pb/irm.proto') diff --git a/src/lib/pb/irm.proto b/src/lib/pb/irm.proto index 98b75a95..f54bc9ea 100644 --- a/src/lib/pb/irm.proto +++ b/src/lib/pb/irm.proto @@ -100,4 +100,5 @@ message irm_msg { optional sint32 cipher_nid = 27; /* cipher NID */ optional uint32 generation = 28; /* re-key batch generation */ optional bool rekey = 29; /* re-key watermark trigger */ + optional bool rk_initiator = 30; /* re-key proof-holder side */ } -- cgit v1.2.3