Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Chris Nandor <pudge@pobox.com>
Cc: linux-audit@redhat.com
Subject: Re: USER_CMD
Date: Thu, 14 Jul 2016 15:06:20 -0400	[thread overview]
Message-ID: <2500772.GKlpCM7XVk@x2> (raw)
In-Reply-To: <CAHcE2wrcXyskQOoKnt=bnhjjXn5NVCPRMB3w+icAugXBRknzEA@mail.gmail.com>

On Thursday, July 14, 2016 10:44:46 AM EDT Chris Nandor wrote:
> Sorry, I guess I should have been more clear ... what sort of rule would
> make it show up?  I'm not seeing it.

Its hardwired. You don't need to add a rule. The rules that you add always 
result in SYSCALL events. You should also add a key to every rule as a 
reminder of what it means. So, any SYSCALL event that does not have a key is 
trigger by something else like a SELinux AVC.

-Steve

> On Thu, Jul 14, 2016 at 10:37 AM, Steve Grubb <sgrubb@redhat.com> wrote:
> > On Thursday, July 14, 2016 10:22:30 AM EDT Chris Nandor wrote:
> > > How does one get USER_CMD records into the audit.log?
> > 
> > The sudo command is the usual way.
> > 
> > -Steve
> > 
> > --
> > Linux-audit mailing list
> > Linux-audit@redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2016-07-14 19:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 17:22 USER_CMD Chris Nandor
2016-07-14 17:37 ` USER_CMD Steve Grubb
2016-07-14 17:44   ` USER_CMD Chris Nandor
2016-07-14 19:06     ` Steve Grubb [this message]
2016-07-14 19:44       ` USER_CMD Chris Nandor
2016-07-14 19:50         ` USER_CMD Steve Grubb
2016-07-14 21:28           ` USER_CMD Chris Nandor

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=2500772.GKlpCM7XVk@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=pudge@pobox.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