From: Casey Schaufler <casey@schaufler-ca.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Chris Wright <chrisw@sous-sol.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>,
Eric Paris <eparis@parisplace.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Security Modules List
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] security: remove security_sb_post_mountroot hook
Date: Sat, 29 Dec 2007 16:29:29 -0800 (PST) [thread overview]
Message-ID: <139407.71031.qm@web36615.mail.mud.yahoo.com> (raw)
In-Reply-To: <200712300020.lBU0KPcr010209@tazenda.hos.anvin.org>
--- "H. Peter Anvin" <hpa@zytor.com> wrote:
> The security_sb_post_mountroot() hook is long-since obsolete, and is
> fundamentally broken: it is never invoked if someone uses initramfs.
> This is particularly damaging, because the existence of this hook has
> been used as motivation for not using initramfs.
>
> Stephen Smalley confirmed on 2007-07-19 that this hook was originally
> used by SELinux but can now be safely removed:
>
> http://marc.info/?l=linux-kernel&m=118485683612916&w=2
>
> Cc: Stephen Smalley <sds@tycho.nsa.gov>
> Cc: James Morris <jmorris@namei.org>
> Cc: Eric Paris <eparis@parisplace.org>
> Cc: Chris Wright <chrisw@sous-sol.org>
> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
It is also the case that Smack does not use this hook.
It can be removed as far as I'm concerned.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2007-12-30 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 0:20 [PATCH] security: remove security_sb_post_mountroot hook H. Peter Anvin
2007-12-30 0:29 ` Casey Schaufler [this message]
2007-12-30 5:07 ` James Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=139407.71031.qm@web36615.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=eparis@parisplace.org \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.