or should block size for xts.c set to 1 instead of AES block size?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: or should block size for xts.c set to 1 instead of AES block size?
From: Kestrel seventyfour <kestrelseventyfour@xxxxxxxxx>
Date: Fri, 7 May 2021 08:12:36 +0200

Hi,

one more thought, shouldn't the block size for generic xts set to 1 in
order to reflect that any input size length is allowed to the
algorithm?

Thanks.

Follow-Ups:
- Re: or should block size for xts.c set to 1 instead of AES block size?
  - From: Ard Biesheuvel

Prev by Date: xts.c and block size inkonsistency? cannot pass generic driver comparision tests
Next by Date: Re: xts.c and block size inkonsistency? cannot pass generic driver comparision tests
Previous by thread: xts.c and block size inkonsistency? cannot pass generic driver comparision tests
Next by thread: Re: or should block size for xts.c set to 1 instead of AES block size?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel] [Gnu Classpath] [Gnu Crypto] [DM Crypt] [Netfilter] [Bugtraq]

Powered by Linux