public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Granting CAP_AUDIT_WRITE to X/dbus/...
Date: Mon, 15 Sep 2014 09:57:44 -0400	[thread overview]
Message-ID: <1786181.n8Vjayl5bq@x2> (raw)
In-Reply-To: <20140915132003.799cae6d@soldur.bigon.be>

On Monday, September 15, 2014 01:20:03 PM Laurent Bigonville wrote:
> Hello,
> 
> I was wondering now that the xserver can run as non-root shouldn't the
> CAP_WRITE_AUDIT file capability be set on the Xorg executable?

I can't imagine what the Xserver would need to do with auditing. If its linked 
against libaudit, then I guess it needs it. That said, no one has asked me to 
review what the Xserver is doing wrt auditing. So, I have no idea if its 
actually correctly done.


> Same question for AVC denials logging with dbus session bus[0]?

That one I know needs to write events.


> And in general, does anybody has an opinion about giving this
> capability to $random executable?

Yep, it should be done very cautiously. Some upstreams think audit is a syslog 
and just absolutely mess it up. Even upstreams that I helped get audit events 
working eventually decide to make changes (for who knows what reason) and then 
I find out a year later that they messed things up.

So, if auditing is being added to $random program, be suspicious and ask on 
the list if this is known and correct. I am wanting to fix this by creating 
some test suites that can help identify when programs change and start doing 
the wrong thing.

-Steve


> Cheers,
> 
> Laurent Bigonville
> 
> [0] See: https://bugs.freedesktop.org/show_bug.cgi?id=83856
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2014-09-15 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 11:20 Granting CAP_AUDIT_WRITE to X/dbus/ Laurent Bigonville
2014-09-15 13:57 ` Steve Grubb [this message]
2014-09-15 22:17   ` Daniel J Walsh

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=1786181.n8Vjayl5bq@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    /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