linux-kernel - Re: About git-bisect (defconfigs)

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]

Message-ID: <20081204001452.GH11807@mail.local.tull.net>
Date:	Thu, 4 Dec 2008 11:14:52 +1100
From:	Nick Andrew <nick@...k-andrew.net>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Francis Moreau <francis.moro@...il.com>,
	"Renato S. Yamane" <yamane@...mondcut.com.br>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: About git-bisect (defconfigs)

On Wed, Dec 03, 2008 at 09:50:51AM -0800, Randy Dunlap wrote:
> 2.  There are several security-related config items that default to =y but the
> kconfig help says:  If unsure, say N here.  Like:
> 
> 
> CONFIG_NETLABEL=y
> CONFIG_NETWORK_SECMARK=y
> CONFIG_KEYS=y
> CONFIG_SECURITY=y
> CONFIG_SECURITY_NETWORK=y
> CONFIG_SECURITY_SELINUX=y
> 
> Maybe I just don't understand the current meaning/usage of defconfig.  eh?

A consistent approach to the Kconfig hints would help. To me,
"If unsure, say N" implies that turning off the feature won't break
the kernel nor be anything particularly important. The Kconfig hints
should follow the defaults (or else why default to 'y'?) for common
architectures.

Perhaps menuconfig can generate the "If unsure" message itself from
the architecture defaults? That will ensure consistency.

Nick.

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