linux-kernel - Re: [PATCH] reboot: disable usermodehelper to prevent fs access

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:	Thu, 5 May 2011 14:34:58 -0700
From:	Greg KH <greg@...ah.com>
To:	Valdis.Kletnieks@...edu
Cc:	Kay Sievers <kay.sievers@...y.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] reboot: disable usermodehelper to prevent fs access

On Thu, May 05, 2011 at 05:24:25PM -0400, Valdis.Kletnieks@...edu wrote:
> On Thu, 05 May 2011 13:32:05 +0200, Kay Sievers said:
> 
> > In case CONFIG_UEVENT_HELPER_PATH is not set to "", which it
> > should be on every system
> 
> If it indeed should be that on every system, shouldn't it be listed
> in feature-removal-schedule.txt?

It's the default value, but distros, and people, can and do override it
for various reasons.  Why would it be added to
feature-removal-schedule.txt?

> Does anybody have a running list of "Stuff we set by default at one time, but
> no longer recommend"?

Look at the default values for different configurations options and why
they differ in your system is about the only way that I know of, sorry.

thanks,

greg k-h
--
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/