| 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
| ||
|
Message-Id: <200905071441.27093.jarod@redhat.com> Date: Thu, 7 May 2009 14:41:26 -0400 From: Jarod Wilson <jarod@...hat.com> To: linux-crypto@...r.kernel.org Cc: linux-kernel@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au>, Neil Horman <nhorman@...driver.com> Subject: [PATCH 0/2] crypto: disallow non-approved algs in fips mode At present, nothing is preventing the use of non-approved algorithms in fips mode. I was initially working on a patch to make it easier for all fips-approved algs to be tested using tcrypt, and realized the changes I was making could also be used to prevent non-approved algs in fips mode. Any approved alg *must* have self-tests, and thus have an entry in testmgr.c's alg_test_descs[]. By adding a fips flag to these entries, we can simply reject all algs that don't have this flag when in fips mode by skipping their self-tests and returning an -EINVAL to prevent them from being loaded. So with this change, I can 1) 'modprobe tcrypt' and have all fips approved algs self-tested, and *only* fips approved algs tested 2) 'modprobe md4' for example, and in fips mode, have the module load rejected as invalid Patch 1/2 adds the basic infra Patch 2/2 marks the allowed algs -- Jarod Wilson jarod@...hat.com -- 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