Date: Thu, 13 Jan 2022 14:48:11 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261172] GELI boot failing with aes_xts_reinit: invalid IV length Message-ID: <bug-261172-227-uvH5C68SY7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261172-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261172 Mikael Urankar <mikael@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikael@FreeBSD.org --- Comment #1 from Mikael Urankar <mikael@FreeBSD.org> --- Same here, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261172 I've had to revert all the latest changes in sys/opencrypto and the one in stand (geliboot: Use the multi-block functions for AES-XTS.). I don't know which one is causing the problem, reverting only 'geliboot: Use the multi-block functions for AES-XTS.' doesn't fix it. cryptosoft: Use multi-block encrypt/decrypt for ChaCha20-Poly1305 cryptosoft: Use multi-block encrypt/decrypt for AES-CCM cryptosoft: Use multi-block encrypt/decrypt for AES-GCM swcr_encdec: Rename blks to blkszcryptosoft: Use multi-block encrypt/decrypt for non-AEAD ciphers. crypto: Re-add encrypt/decrypt_multi hooks to enc_xform. crypto: Add support for the XChaCha20-Poly1305 AEAD cipher geliboot: Use the multi-block functions for AES-XTS. It's on a core i7 3540m cpu if that matters. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261172-227-uvH5C68SY7>