Page MenuHomeFreeBSD

Use G_ELI_IVKEYLEN as the size of IV in the user test code.
ClosedPublic

Authored by jhb on Jan 13 2022, 9:28 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Dec 7, 5:36 AM
Unknown Object (File)
Sat, Dec 6, 2:06 AM
Unknown Object (File)
Tue, Nov 25, 4:08 AM
Unknown Object (File)
Wed, Nov 19, 7:26 AM
Unknown Object (File)
Fri, Nov 14, 9:52 PM
Unknown Object (File)
Nov 13 2025, 5:32 PM
Unknown Object (File)
Oct 27 2025, 9:23 AM
Unknown Object (File)
Oct 25 2025, 6:09 AM
Subscribers

Details

Summary

IVs are not the size of keys as a general case. Most often they are
the size of a single block.

Sponsored by: The FreeBSD Foundation

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 43912
Build 40800: arc lint + arc unit

Event Timeline

jhb requested review of this revision.Jan 13 2022, 9:28 PM

Do you need a kassert G_ELI_IVKEYLEN >= keysize?

This revision is now accepted and ready to land.Jan 13 2022, 9:51 PM
In D33885#766236, @imp wrote:

Do you need a kassert G_ELI_IVKEYLEN >= keysize?

No, the entire point is that IV sizes have no relation to key sizes. For the ciphers involved in fact, the key sizes are generally larger than the IVs (e.g. 8 byte IV for AES-XTS vs a 256/512 bit key).