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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 26 Aug 2010 00:50:36 +0200
From:	Samuel Thibault <Samuel.Thibault@...-lyon.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Sebastien Hinderer <Sebastien.Hinderer@...-lyon.org>,
	Andreas Mohr <andi@...as.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Len Brown <len.brown@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: EuroBraille/Iris power off

H. Peter Anvin, le Wed 25 Aug 2010 14:19:55 -0700, a écrit :
> At that point I'd almost prefer doing something like a BIOS signature
> check if we can't do anything better.

Well, there will be several versions of the BIOS signature, which the
constructor is not likely to provide.

Just to make sure there's no misunderstanding: it was never planned that
this driver be loaded unless some manual intervention, like explicitly
loadling the module or setting some parameter, so that if bad effects
happen on the machine, the user can only get angry at himself for having
loaded by hand a random module without reading the documentation that
explicitly says (twice) it's only for a particular kind of hardware.

I however now realize that I don't find a way to force a driver to be
compiled only as a module.  If there isn't, I guess we can just add
a module parameter to enable/disable the driver, so that it won't be
active by default even compiled-in?

Samuel
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ