linux-kernel - Re: [PATCH] CONFIG_CC_STACKPROTECTOR is no longer experimental

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]

Message-ID: <1341597439.4655.23.camel@amber.site>
Date:	Fri, 06 Jul 2012 19:57:19 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH] CONFIG_CC_STACKPROTECTOR is no longer experimental

Hi Randy,

Le vendredi 06 juillet 2012 à 10:23 -0700, Randy Dunlap a écrit :
> On 07/06/2012 07:08 AM, Jean Delvare wrote:
> 
> > This feature has been around for over 5 years now, so I presume it is
> > no longer considered experimental.
> > 
> > Signed-off-by: Jean Delvare <jdelvare@...e.de>
> > Cc: Ingo Molnar <mingo@...hat.com>
> > Cc: Arjan van de Ven <arjan@...ux.intel.com>
> > Cc: Andi Kleen <andi@...stfloor.org>
> > ---
> > Or is there any reason to still consider this an experimental feature?
> 
> 
> I doubt it, but if it is still experimental, it should also have
> 	depends on EXPERIMENTAL

Agreed.

> and then it would be nice if kconfig (the software) would add the
>   " (EXPERIMENTAL)" tag when it sees such a dependency.

Oh yeah, I've been dreaming of this for years now but never found the
time to actually look into implementing it. Not sure if I would actually
be able to anyway, as it will probably require some Kconfig magic beyond
my knowledge.


-- 
Jean Delvare
Suse L3

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