public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Beattie <sbeattie@suse.de>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-audit@redhat.com
Subject: Re: proc_loginuid_write() checks wrong capability?
Date: Tue, 6 Feb 2007 11:53:32 -0800	[thread overview]
Message-ID: <20070206195332.GD6698@suse.de> (raw)
In-Reply-To: <1170788918.12293.422.camel@moss-spartans.epoch.ncsc.mil>


[-- Attachment #1.1: Type: text/plain, Size: 663 bytes --]

On Tue, Feb 06, 2007 at 02:08:38PM -0500, Stephen Smalley wrote:
> Setting the loginuid of a process is a form of "control" over the audit
> system, as the loginuid is the basis for user accountability in the
> audit framework.    It differs from merely generating a user audit
> message.  There was some discussion of introducing a third audit
> capability, but no support for it.

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.

-- 
Steve Beattie
SUSE Labs, Novell Inc. 
<sbeattie@suse.de>
http://NxNW.org/~steve/

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2007-02-06 19:53 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 [this message]
2007-02-06 21:47     ` Casey Schaufler
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=20070206195332.GD6698@suse.de \
    --to=sbeattie@suse.de \
    --cc=linux-audit@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox