Juergen Christ cd854f225b Fix GHASH-ASM implementation on s390x ... s390x GHASH assembler implementation assumed it was called from a gcm128_context structure where the Xi paramter to the ghash function was embedded in that structure. Since the structure layout resembles the paramter block required for kimd-GHASH, the assembler code simply assumed the 128 bytes after Xi are the hash subkey. This assumption was broken with the introduction of AES-GCM-SIV which uses the GHASH implementation without a gcm128_context structure. Furthermore, the bytes following the Xi input parameter to the GHASH function do not contain the hash subkey. To fix this, we remove the assumption about the calling context and build the parameter block on the stack. This requires some copying of data to and from the stack. While this introduces a performance degradation, new systems anyway use kma for GHASH/AES-GCM. Finally fixes #18693 for s390x. Signed-off-by: Juergen Christ <jchrist@linux.ibm.com> Reviewed-by: Todd Short <todd.short@me.com> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/18939)		2022-08-09 10:52:08 +01:00
..
asm	Fix GHASH-ASM implementation on s390x	2022-08-09 10:52:08 +01:00
build.info	Rename x86-32 assembly files from .s to .S.	2022-05-24 13:16:06 +10:00
cbc128.c
ccm128.c
cfb128.c
ctr128.c
cts128.c
gcm128.c	Implement AES-GCM-SIV (RFC8452)	2022-07-29 08:32:16 -04:00
ocb128.c
ofb128.c
siv128.c
wrap128.c
xts128.c