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
| ||
|
Date: Fri, 31 Aug 2012 20:31:46 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Eric Paris <eparis@...isplace.org> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org, James Morris <james.l.morris@...cle.com>, Eric Paris <eparis@...hat.com>, Jiri Kosina <jkosina@...e.cz>, John Johansen <john.johansen@...onical.com>, Dan Carpenter <dan.carpenter@...cle.com>, Al Viro <viro@...iv.linux.org.uk>, linux-security-module@...r.kernel.org Subject: Re: [PATCH] security: unconditionally call Yama Eric Paris <eparis@...isplace.org> writes: > On Fri, Aug 31, 2012 at 4:59 PM, Eric W. Biederman > <ebiederm@...ssion.com> wrote: > >> From a overal kernel maintenance and use perspective the unconditional >> enablement is a pain. >> >> We long ago established the principle that compiling additional code >> into the kernel should not change the semenatics of the kernel. >> >> So this code needs to come with a command line or sysctl on/off switch >> not an unconditional enable. > > Your argument makes zero sense. If I decide to build new code, that > new code can do something. Sure but it should not change the existing behavior without being configured to. This comes out of the practice that kernels that need to support a wide variety of use cases enable everything by default. Having to vet kernel options for will this make my kernel do strange things if this option is enabled, massively increase the burden on people building and supporting kernels. > It happens all the time. If you don't like Yama, don't build Yama. > If you don't like the only thing that Yama does (it only implements > one protection), disable that protection from sysctl. I don't get it. Having taken the time now to vet Yama ugh. Having Yama enabled if simply compiled in breaks using gdb to attach to a process runing in another window. Talk about something you don't want to surprise someone with. It is very much not ok to have that be enabled by default just because it happens to be compiled in. Eric -- 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