summaryrefslogtreecommitdiff
path: root/sys/man
diff options
context:
space:
mode:
authorcinap_lenrek <cinap_lenrek@felloff.net>2017-11-12 23:15:15 +0100
committercinap_lenrek <cinap_lenrek@felloff.net>2017-11-12 23:15:15 +0100
commit3356e0e731bb8e0f4c82caebe358fae2c8fc9113 (patch)
treea92fcc0632401e8a1701f6b386c180ec6f7317c9 /sys/man
parent4f27f6a04f8c8709e20767b50bd7c2a22ab29340 (diff)
libsec: AES-NI support for amd64
Add assembler versions for aes_encrypt/aes_decrypt and the key setup using AES-NI instruction set. This makes aes_encrypt and aes_decrypt into function pointers which get initialized by the first call to setupAESstate(). Note that the expanded round key words are *NOT* stored in big endian order as with the portable implementation. For that reason the AESstate.ekey and AESstate.dkey fields have been changed to void* forcing an error when someone is accessing the roundkey words. One offender was aesXCBmac, which doesnt appear to be used and the code looks horrible so it has been deleted. The AES-NI implementation is for amd64 only as it requires the kernel to save/restore the FPU state across syscalls and pagefaults.
Diffstat (limited to 'sys/man')
-rw-r--r--sys/man/2/aes43
1 files changed, 20 insertions, 23 deletions
diff --git a/sys/man/2/aes b/sys/man/2/aes
index 19849657c..d60586c4f 100644
--- a/sys/man/2/aes
+++ b/sys/man/2/aes
@@ -7,7 +7,6 @@ aesCFBencrypt, \
aesCFBdecrypt, \
aesOFBencrypt, \
aes_xts_encrypt, aes_xts_decrypt, \
-setupAESXCBCstate, aesXCBCmac, \
setupAESGCMstate, \
aesgcm_setiv, aesgcm_encrypt, aesgcm_decrypt \
- advanced encryption standard (rijndael)
@@ -22,14 +21,15 @@ aesgcm_setiv, aesgcm_encrypt, aesgcm_decrypt \
.PP
.in +0.5i
.ti -0.5i
+.PP
.B
-void aes_encrypt(ulong rk[], int Nr, uchar pt[16], uchar ct[16]);
+void aes_encrypt(ulong rk[], int Nr, uchar pt[16], uchar ct[16])
.PP
.B
-void aes_decrypt(ulong rk[], int Nr, uchar ct[16], uchar pt[16]);
+void aes_decrypt(ulong rk[], int Nr, uchar ct[16], uchar pt[16])
.PP
.B
-void setupAESstate(AESstate *s, uchar key[], int keybytes, uchar *ivec)
+void setupAESstate(AESstate *s, uchar key[], int nkey, uchar *ivec)
.PP
.B
void aesCBCencrypt(uchar *p, int len, AESstate *s)
@@ -53,12 +53,6 @@ void aes_xts_encrypt(AESstate *tweak, AESstate *ecb, uvlong sectorNumber, uchar
void aes_xts_decrypt(AESstate *tweak, AESstate *ecb, uvlong sectorNumber, uchar *input, uchar *output, ulong len)
.PP
.B
-void setupAESXCBCstate(AESstate *s)
-.PP
-.B
-void aesXCBCmac(uchar *p, int len, AESstate *s)
-.PP
-.B
void setupAESGCMstate(AESGCMstate *s, uchar *key, int keylen, uchar *iv, int ivlen)
.PP
.B
@@ -78,7 +72,7 @@ and
are the block ciphers, corresponding to
.IR des (2)'s
.IR block_cipher .
-.IR AesCBCencrypt ,
+.I AesCBCencrypt
and
.I aesCBCdecrypt
implement cipher-block-chaining encryption.
@@ -94,10 +88,20 @@ and
implement the XTS-AES tweakable block cipher, per IEEE 1619-2017 (see bugs below).
.IR SetupAESstate
is used to initialize the state of the above encryption modes.
-.I SetupAESXCBCstate
+The expanded roundkey parameters
+.I rk
+and
+.I Nr
+of
+.I aes_encrypt
+and
+.I aes_decrypt
+are returned in
+.I AESstate.ekey
and
-.I aesXCBCmac
-implement AES XCBC message authentication, per RFC 3566.
+.I AESstate.dkey
+with the corresponding number of rounds in
+.IR AESstate.rounds .
.IR SetupAESGCMstate ,
.IR aesgcm_setiv ,
.I aesgcm_encrypt
@@ -116,7 +120,8 @@ arguments.
Aesgcm_decrypt returns zero when authentication and decryption where successfull and
non-zero otherwise.
All ciphering is performed in place.
-.I Keybytes
+The byte keysize
+.I nkey
should be 16, 24, or 32.
The initialization vector
.I ivec
@@ -144,14 +149,6 @@ in
.br
.B http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf
.SH BUGS
-The functions
-.IR aes_encrypt ,
-.IR aes_decrypt ,
-.IR setupAESXCBCstate ,
-and
-.IR aesXCBCmac
-have not yet been verified by running test vectors through them.
-.PP
Because of the way that non-multiple-of-16 buffers are handled,
.I aesCBCdecrypt
must be fed buffers of the same size as the