public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Matt Anderson <mra@hp.com>
Cc: 'linux-audit' <linux-audit@redhat.com>
Subject: Re: [PATCH]Fix me add subj
Date: Wed, 27 Aug 2008 12:53:32 -0400	[thread overview]
Message-ID: <200808271253.33122.sgrubb@redhat.com> (raw)
In-Reply-To: <20080827160426.GA10066@ldl.fc.hp.com>

On Wednesday 27 August 2008 12:04:26 Matt Anderson wrote:
> On Tue, Aug 26, 2008 at 04:08:35PM -0400, Steve Grubb wrote:
> > On Tuesday 26 August 2008 15:55:51 Stephen Smalley wrote:
> > > 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.
>
> Can we be sure the delayed translation will be correct?

I don't plan to add translations any time soon. We also don't have time to do 
a translation while logging. So, we will just have raw data for a while.


> It seems to me that by then the policy or the translation could have changed
> and although you may have an audit of that event you wouldn't necessarily be
> able to reconstruct the context that should appear in the log.

True and something that will need to be worked around.

-Steve

  reply	other threads:[~2008-08-27 16:53 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 [this message]
2008-08-27 21:26       ` Casey Schaufler
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=200808271253.33122.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=mra@hp.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