From: Chris Wright <chrisw@osdl.org>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: "Serge E. Hallyn" <hallyn@cs.wm.edu>,
Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
James Morris <jmorris@redhat.com>, Chris Wright <chrisw@osdl.org>
Subject: Re: [PATCH] Fix audit control message checks
Date: Tue, 18 Jan 2005 11:30:07 -0800 [thread overview]
Message-ID: <20050118113007.Y24171@build.pdx.osdl.net> (raw)
In-Reply-To: <1106055058.18274.57.camel@moss-spartans.epoch.ncsc.mil>; from sds@epoch.ncsc.mil on Tue, Jan 18, 2005 at 08:30:58AM -0500
* Stephen Smalley (sds@epoch.ncsc.mil) wrote:
> On Sat, 2005-01-15 at 15:07, Serge E. Hallyn wrote:
> > The audit control messages are sent over netlink. Permission checks
> > are done on the process receiving the message, which may not be the
> > same as the process sending the message. This patch switches the
> > netlink_send security hooks to calculate the effective capabilities
> > based on the sender. Then audit_receive_msg performs capability checks
> > based on that.
> >
> > It also introduces the CAP_AUDIT_WRITE and CAP_AUDIT_CONTROL capabilities,
> > and replaces the previous CAP_SYS_ADMIN checks in audit code with the
> > appropriate checks.
> >
> > Please apply.
> >
> > Changelog:
> > 1/15/2005: Simplified dummy_netlink_send given that dummy now
> > keeps track of capabilities.
> > 1/14/2005: Many fixes based on feedback from linux-audit@redhat.com
> > list.
> > 1/14/2005: Removed the netlink_msg_type helper function.
> > 1/07/2005: Swith to using CAP_AUDIT_WRITE and CAP_AUDIT_CONTROL.
> >
> > thanks,
> > -serge
> >
> > Signed-off-by: Serge Hallyn <serue@us.ibm.com>
>
> Signed-off-by: Stephen Smalley <sds@epoch.ncsc.mil>
Signed-off-by: Chris Wright <chrisw@osdl.org>
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2005-01-18 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 20:07 Serge E. Hallyn
2005-01-18 13:30 ` Stephen Smalley
2005-01-18 19:30 ` Chris Wright [this message]
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=20050118113007.Y24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=hallyn@cs.wm.edu \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®