From: Casey Schaufler <casey@schaufler-ca.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: 'linux-audit' <linux-audit@redhat.com>
Subject: Re: [PATCH]Fix me add subj
Date: Wed, 27 Aug 2008 14:26:13 -0700 [thread overview]
Message-ID: <48B5C675.6010307@schaufler-ca.com> (raw)
In-Reply-To: <200808261608.36217.sgrubb@redhat.com>
Steve Grubb wrote:
> On Tuesday 26 August 2008 15:55:51 Stephen Smalley wrote:
>
>> On Tue, 2008-08-26 at 15:34 -0400, Steve Grubb wrote:
>>
>>> On Monday 18 August 2008 06:04:25 Chu Li wrote:
>>>
>>>> I have made a patch for "Fixme add subj" in auditd.c. This is for the
>>>> latest codes.
>>>>
>>> Now that the audit svn is open for new work...I started to apply this
>>> patch. But then I got to thinking about SMACK. It probably does not like
>>> us to get selinux labels. I was wondering if we need to try to get its
>>> label, too? And I was wondering if both SE Linux and SMACK could be
>>> running at the same time? If they can, do we collect both labels?
>>>
>> They are exclusive of one another, and they both provide the process
>> label via /proc/pid/attr/current. libselinux wraps that kernel
>> interface with getcon() (for current context) and getpidcon() (for
>> context of a given pid), which internally handle the allocation of the
>> buffer and will deal with label translation if using mcstransd.
>>
>> So if you want the code to work with either, you'd directly
>> read /proc/pid/attr/current and display the resulting string. If you
>> want to be SELinux-specific and include functionality like MLS label
>> translation, you'd use getpidcon(3).
>>
>
> Thanks, that's very helpful. I think we want the raw data and then do context
> translations later in the parsing library if someone asks for it
That works for Smack.
Thank you.
next prev parent reply other threads:[~2008-08-27 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 10:04 [PATCH]Fix me add subj Chu Li
2008-08-19 20:34 ` Steve Grubb
2008-08-26 19:34 ` Steve Grubb
2008-08-26 19:55 ` Stephen Smalley
2008-08-26 20:08 ` Steve Grubb
2008-08-27 16:04 ` Matt Anderson
2008-08-27 16:53 ` Steve Grubb
2008-08-27 21:26 ` Casey Schaufler [this message]
2008-08-28 18:41 ` Steve Grubb
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=48B5C675.6010307@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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 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.