From: Steve Grubb <sgrubb@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: Capabilities audit field
Date: Mon, 13 Oct 2008 19:27:20 -0400 [thread overview]
Message-ID: <200810131927.20437.sgrubb@redhat.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0810140953220.25832@tundra.namei.org>
On Monday 13 October 2008 18:54:50 James Morris wrote:
> > 570 case AVC_AUDIT_DATA_CAP:
> > 571 audit_log_format(ab, " capability=%d",
> > a->u.cap); 572 break;
>
> Nope, the capability number is correctly recorded in a->u.cap, and you'll
> also see capability2 as the tclass value.
avc: denied { ipc_owner } for pid=4653 comm="ntpd" capability=15
scontext=root:system_r:ntpd_t tcontext=root:system_r:ntpd_t
tclass=capability
Hmm...the tclass field, being at the end, has not been parsed at the moment I
need it to decide what capability we are talking about. tclass really should
have been moved up nearer the beginning if its being used to determine how to
interpret other fields. It would be nicer if there was some hint at whether
we are dealing with a cap1 or cap2 capability before the capability field. I
guess my other choice is to drop interpretation of capabilities in ausearch
since now I don't know which set to use until after I've already printed what
I thought it was.
-Steve
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-10-13 23:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 13:07 Capabilities audit field Steve Grubb
2008-10-12 23:12 ` James Morris
2008-10-13 10:35 ` Steve Grubb
2008-10-13 22:54 ` James Morris
2008-10-13 23:27 ` Steve Grubb [this message]
2008-10-14 9:21 ` James Morris
2008-10-14 13:35 ` Stephen Smalley
2008-10-12 23:18 ` Joshua Brindle
2008-10-13 4:05 ` James Morris
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=200810131927.20437.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=jmorris@namei.org \
--cc=selinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.