From: Casey Schaufler <casey@schaufler-ca.com>
To: Steve Beattie <sbeattie@suse.de>
Cc: linux-audit@redhat.com
Subject: Re: proc_loginuid_write() checks wrong capability?
Date: Tue, 6 Feb 2007 13:47:24 -0800 (PST) [thread overview]
Message-ID: <20070206214724.63499.qmail@web36614.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070206195332.GD6698@suse.de>
--- Steve Beattie <sbeattie@suse.de> wrote:
> Ah, thanks Stephen and Casey, for explaining the
> reasoning. It does have
> the unfortunate side effect of causing
> CAP_AUDIT_CONTROL to be needed
> more widely than one might expect.
The appropriate granularity of capabilities
has always been and will always be a
contentious issue, with the fashion shifting
whimsically. Writing audit records is pretty
clearly a different beast than setting audit
attributes, but since there is significant
overlap between the programs that set audit
state and those that write audit records you
could make a case for either making a seperate
capability for setting the loginid or for
having a single CAP_AUDIT. Heck, at one time
or another I've argued each way. I expect that
the current granularity is sufficiently
obvious and useful to leave alone, at least
for the time being.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2007-02-06 21:47 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 [this message]
2007-02-06 19:15 ` Casey Schaufler
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=20070206214724.63499.qmail@web36614.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