From: LC Bruzenak <lenny@magitekltd.com>
To: linux-audit@redhat.com
Subject: key options with spaces
Date: Tue, 11 Jun 2013 16:04:54 -0500 [thread overview]
Message-ID: <51B790F6.7090306@magitekltd.com> (raw)
I was playing with audit rules using keys with spaces.
Is the following expected (ignore the logic; was just testing the returns)?
# auditctl -l -k lsmod
LIST_RULES: exit,always watch=/sbin/lsmod perm=x key=lsmod kernel
LIST_RULES: exit,always watch=/bin/ping perm=x key=lsmod ping
Thx,
LCB
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next reply other threads:[~2013-06-11 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 21:04 LC Bruzenak [this message]
2013-06-11 21:32 ` key options with spaces LC Bruzenak
2013-06-19 12:34 ` Steve Grubb
2013-06-19 18:49 ` LC Bruzenak
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=51B790F6.7090306@magitekltd.com \
--to=lenny@magitekltd.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