| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 28 Oct 2014 15:40:09 -0200 From: "Leonidas S. Barbosa" <leosilva@...ux.vnet.ibm.com> To: linux-crypto@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net> Cc: linux-kernel@...r.kernel.org, Marcelo Henrique Cerri <mhcerri@...ux.vnet.ibm.com>, Fionnuala Gunter <fin@...ux.vnet.ibm.com> Subject: [PATCH 0/9] NX crypto driver fixes This patch set fixes the follow issues in NX crypto driver: - Bound limit issue that causes a memory crash - SHA concurrence issue - IV vector fix with the correct bit order - NX CCM does not support keys larger than 128 causing crashes in fips mode. Leonidas S. Barbosa (9): Moving NX-AES-CBC to be process logic Moving NX-AES-CCM to be process logic and sg_list bounds Moving limit and bound logic in CTR and fix IV vector Moving NX-AES-ECB to be processed logic Moving NX-AES-GCM to be processed logic Moving NX-AES-XCBC to be processed logic Fix SHA concurrence issue and sg limit bounds Fixing the limit number of bytes to be processed Disable ccm and ccm4309 in fips mod drivers/crypto/nx/nx-aes-cbc.c | 12 +-- drivers/crypto/nx/nx-aes-ccm.c | 61 +++++------ drivers/crypto/nx/nx-aes-ctr.c | 13 +-- drivers/crypto/nx/nx-aes-ecb.c | 12 +-- drivers/crypto/nx/nx-aes-gcm.c | 66 +++++++----- drivers/crypto/nx/nx-aes-xcbc.c | 81 +++++++++++--- drivers/crypto/nx/nx-sha256.c | 208 ++++++++++++++++++------------------- drivers/crypto/nx/nx-sha512.c | 222 ++++++++++++++++++--------------------- drivers/crypto/nx/nx.c | 159 +++++++++++++++++++++++----- drivers/crypto/nx/nx.h | 8 +- 10 files changed, 469 insertions(+), 373 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists