From: Casey Schaufler <casey@schaufler-ca.com>
To: Steve Beattie <sbeattie@suse.de>, linux-audit@redhat.com
Subject: Re: proc_loginuid_write() checks wrong capability?
Date: Tue, 6 Feb 2007 11:15:22 -0800 (PST) [thread overview]
Message-ID: <20070206191522.23902.qmail@web36615.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070206182715.GA25164@suse.de>
--- Steve Beattie <sbeattie@suse.de> wrote:
> Hi,
>
> Looking at the code for proc_loginuid_write() in
> Linus' git tree, the
> capability CAP_AUDIT_CONTROL is needed to write to
> /proc/pid/loginuid
> and generate LOGIN type records. This seems to run
> counter to the
> capabilities(7) manpage, which suggests that
> CAP_AUDIT_CONTROL is to
> "Enable and disable kernel auditing; change auditing
> filter rules;
> retrieve auditing status and filtering rules",
> whereas CAP_AUDIT_WRITE
> is to "Allow records to be written to kernel
> auditing log."
>
> Should the following patch be applied, or am I
> misunderstanding something?
The latter. CAP_AUDIT_WRITE allows you to
create audit records, and that's it. It does
not allow you to change how they're managed,
which is an important aspect of the loginuid
of a process. Updating the loginuid changes
information that will go into audit records,
and that is strongly related to "filtering
rules".
> It doesn't seem quite right that anything
> that makes use of
> pam_loginuid.so should need to be granted the
> capability that allows
> enabling and disabling kernel auditing or changing
> filter rules.
Although the current audit system doesn't
do so (at least, I don't think it does, I
could be wrong) specifiying audit charactoristics
on a per-session basis would require that
capability.
Casey Schaufler
casey@schaufler-ca.com
prev parent reply other threads:[~2007-02-06 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 18:27 proc_loginuid_write() checks wrong capability? Steve Beattie
2007-02-06 19:08 ` Stephen Smalley
2007-02-06 19:53 ` Steve Beattie
2007-02-06 21:47 ` Casey Schaufler
2007-02-06 19:15 ` Casey Schaufler [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=20070206191522.23902.qmail@web36615.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=linux-audit@redhat.com \
--cc=sbeattie@suse.de \
/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