linux-kernel - Re: Default Kconfig state for hw

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Apr 2012 18:35:06 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Nicolas Ferre <nicolas.ferre@...el.com>,
	Olof Johansson <olof@...om.net>, balbi@...com,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org
Subject: Re: Default Kconfig state for hw_random drivers

On Fri, Apr 27, 2012 at 12:55:36PM +0000, Arnd Bergmann wrote:
> On Friday 27 April 2012, Mark Brown wrote:

> > There is one, that's the problem - the driver is defaulting to the same
> > state as the main hw_random option (as is idiomatic for this subsystem).
> > This means that if you've enabled any hw_random device this driver will
> > be enabled by default.  I would argue that this default directive only
> > makes sense if there's an explicit dependency limiting the platforms it
> > can build on.  If it can build on any platform then omitting the default
> > and just defaulting to N as is normal for drivers would be better.

> How about making it default to (HW_RANDOM && ARCH_AT91) then?

Yes, something like that would do the job too.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)