linux-kernel - Re: [PATCH] make CONFIG_EXPERIMENTAL invisible and default

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] [day] [month] [year] [list]

Date:	Sun, 16 Dec 2012 08:19:21 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Jan Engelhardt <jengelh@...i.de>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Kees Cook <keescook@...omium.org>,
	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Serge Hallyn <serge.hallyn@...onical.com>,
	"David S. Miller" <davem@...emloft.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH] make CONFIG_EXPERIMENTAL invisible and default

On Sun, Dec 16, 2012 at 05:29:21AM +0100, Jan Engelhardt wrote:
> 
> On Wednesday 2012-10-03 18:17, Greg Kroah-Hartman wrote:
> >> 
> >> OK, I will bite...  How should I flag an option that is initially only
> >> intended for those willing to take some level of risk?
> >
> >In the text say "You really don't want to enable this option, use at
> >your own risk!"  Or something like that :)
> 
> You know that won't not work, just like "everybody is encouraged
> to upgrade" for -stable. It needs to say "All users must disable this!"

The thought expressed earlier in this thread of unconditionally splatting
during boot seemed pretty compelling to me.  ;-)

							Thanx, Paul

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