| 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: Wed, 20 May 2015 08:29:19 +0200 From: Stephan Mueller <smueller@...onox.de> To: Sandy Harris <sandyinchina@...il.com> Cc: Herbert Xu <herbert@...dor.apana.org.au>, Theodore Ts'o <tytso@....edu>, linux-crypto@...r.kernel.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] random: add random_initialized command line param Am Dienstag, 19. Mai 2015, 18:40:20 schrieb Sandy Harris: Hi Sandy, > >When we do do it, I see no reason to support anything other than 128 >and 256, and I am not sure about retaining 128. Nor do I see any >reason this should be a command-line option rather than just a >compile-time constant. I would hazard to guess that a compile time option is a bit difficult for distributions which typically only want one kernel for all their user base. As that user base is typically large, they would potentially be unable to please everybody with a compile time option. But I see that such a change may not be warranted at this point. Though, I see that discussion may rise again in the future when such new requirements for 256 bit keys (not only AES, thanks Sandy for mentioning :-) ) are commonly raised. So, let us disregard the patch until hard requirements are coming up. Ciao Stephan -- 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