[Bug 263379] [regression] [ipsec] compatibility broken between stable/12 and stable/13 opencrypto in AEAD mode

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 18 Apr 2022 21:05:14 UTC

--- Comment #8 from John Baldwin <jhb@FreeBSD.org> ---
(In reply to Eugene Grosbein from comment #6)

Static keys are not good for AES-GCM or AES-CTR as the sequence number can
rollover yes.  Even for AES-CBC I would be hesitant to rely on static keys
rather than using an IKE daemon to permit dynamic keys.  stable/13 should work
fine with ETA combos such as AES-CBC with SHA1/256/512 HMACs.  Note that the
key for AES-CBC is shorter than for AES-CTR/GCM as it is "only" the actual AES
key (so 16, 24, or 32 bytes) and doesn't include the extra 4 bytes for the
implicit part of the IV.  (And setkey just reports "EINVAL" for all manner of
errors, so it's rather hard to figure out why setkey fails in my experience, so
my best guess is you are reusing the GCM key but need to remove the last 4

The kyua tests test AES-CBC (both 128 and 256 bit keys) with SHA1-HMAC and

In regards to stable/12, yes, I think it is also late and a warning might not
be seen by many users (and almost said as much).  stable/12 is still supported
until 2024 so a 12.4 doesn't seem completely unlikely however.

You are receiving this mail because:
You are on the CC list for the bug.