|| ||Andrew Morton <firstname.lastname@example.org>|
|| ||"Andrew G. Morgan" <email@example.com>|
|| ||Re: [PATCH] per-process securebits|
|| ||Sat, 2 Feb 2008 22:18:12 -0800|
|| ||Linux Security Modules List
firstname.lastname@example.org, "Serge E. Hallyn" <email@example.com>|
On Sat, 02 Feb 2008 22:01:51 -0800 "Andrew G. Morgan" <firstname.lastname@example.org> wrote:
> Here is the very very long version (which took some time to write, and I
> thought was a bit much to spam these lists with):
Thanks. Imagine not testing the retrn value from something like setuid().
Oh well. The reasoning for disabling it was good.
So how do we ever get to the stage where we can recommend that distributors
turn these things on, and have them agree with us?
Do we have sufficiently stern things in place to prevent them from turning
it on by accident? Some of them are pretty gung-ho.
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html