summaryrefslogtreecommitdiffstats
path: root/src/crypto/crypto_null.c
diff options
context:
space:
mode:
authorMichael Brown2022-10-28 17:27:10 +0200
committerMichael Brown2022-11-07 12:19:48 +0100
commit30243ad73957a2e1cc4aedc3f23be66cdf399f00 (patch)
treec0b476b76fed7f2a9c5a3b9ec1ea03f01017a693 /src/crypto/crypto_null.c
parent[tls] Formalise notions of fixed and record initialisation vectors (diff)
downloadipxe-30243ad73957a2e1cc4aedc3f23be66cdf399f00.tar.gz
ipxe-30243ad73957a2e1cc4aedc3f23be66cdf399f00.tar.xz
ipxe-30243ad73957a2e1cc4aedc3f23be66cdf399f00.zip
[crypto] Add concept of cipher alignment size
The GCM cipher mode of operation (in common with other counter-based modes of operation) has a notion of blocksize that does not neatly fall into our current abstraction: it does operate in 16-byte blocks but allows for an arbitrary overall data length (i.e. the final block may be incomplete). Model this by adding a concept of alignment size. Each call to encrypt() or decrypt() must begin at a multiple of the alignment size from the start of the data stream. This allows us to model GCM by using a block size of 1 byte and an alignment size of 16 bytes. As a side benefit, this same concept allows us to neatly model the fact that raw AES can encrypt only a single 16-byte block, by specifying an alignment size of zero on this cipher. Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/crypto/crypto_null.c')
-rw-r--r--src/crypto/crypto_null.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/crypto/crypto_null.c b/src/crypto/crypto_null.c
index 26cfbfc4e..0ad463c3e 100644
--- a/src/crypto/crypto_null.c
+++ b/src/crypto/crypto_null.c
@@ -84,6 +84,7 @@ struct cipher_algorithm cipher_null = {
.name = "null",
.ctxsize = 0,
.blocksize = 1,
+ .alignsize = 1,
.authsize = 0,
.setkey = cipher_null_setkey,
.setiv = cipher_null_setiv,