| 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
| ||
|
Message-ID: <20140624183310.GA4955@kroah.com> Date: Tue, 24 Jun 2014 14:33:10 -0400 From: Greg KH <greg@...ah.com> To: Michael Marineau <mike@...ineau.org> Cc: Alan Stern <stern@...land.harvard.edu>, linux-kernel@...r.kernel.org Subject: Re: CONFIG_UEVENT_HELPER default On Tue, Jun 24, 2014 at 11:30:05AM -0700, Michael Marineau wrote: > On Jun 24, 2014 11:23 AM, "Alan Stern" <stern@...land.harvard.edu> wrote: > > > > Michael and Greg: > > > > The help text for CONFIG_UEVENT_HELPER says (among other things): > > > > This should not be used today, because usual systems create > > many events at bootup or device discovery in a very short time > > frame. > > > > If it shouldn't be used, why does it default to 'y'? > > > > Alan Stern > > > > To introduce the option but not change the default behavior. (yet?) I don't > really have an opinion one way or the other, I just defaulted to being > conservative. Yes, being conservative is good as turning this off with older systems (like the pathological Fedora 3 system that some kernel developers still use for testing), would result in a non-booting box. So if you know that your system is "new enough", it's safe to turn off, but if you have a doubt, leave it on to be safe. 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/
Powered by blists - more mailing lists