From: Amy Griffis <amy.griffis@hp.com>
To: Alexander Viro <aviro@redhat.com>
Cc: Eric Paris <eparis@parisplace.org>,
linux-audit@redhat.com, James Morris <jmorris@namei.org>
Subject: Re: audit-ptrace patch (untested)
Date: Wed, 14 Mar 2007 11:57:00 -0400 [thread overview]
Message-ID: <20070314155700.GA27762@fc.hp.com> (raw)
In-Reply-To: <20070313193909.GH12417@devserv.devel.redhat.com>
Alexander Viro wrote: [Tue Mar 13 2007, 03:39:09PM EDT]
> On Tue, Mar 13, 2007 at 03:00:46PM -0400, Amy Griffis wrote:
> > > + if (sid)
> > > + selinux_sid_to_string(sid, &context->obj_ctx, &len);
> > > +}
> >
> > Why did you choose to do the sid to string conversion at collection
> > time, rather than waiting for audit_log_exit?
>
> Narrower window for sid_to_context to change...
Okay, I hadn't thought of that. But is it really more of a problem for
processes than for ipc or inodes? It's true that processes can change
their context, but that would change the sid, and we've already
collected that data. The sid-to-context-string mapping will only
change on policy load. I see the argument for narrowing the window,
but I'd like to see audit pick one way and stick to it.
Amy
next prev parent reply other threads:[~2007-03-14 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 14:50 audit-ptrace patch (untested) Alexander Viro
2007-03-06 14:46 ` Stephen Smalley
2007-03-07 3:13 ` Alexander Viro
2007-03-07 12:52 ` Stephen Smalley
2007-03-07 16:22 ` James Morris
2007-03-12 12:20 ` Alexander Viro
2007-03-12 13:07 ` Stephen Smalley
2007-03-12 14:16 ` James Morris
2007-03-12 16:19 ` Alexander Viro
2007-03-13 19:00 ` Amy Griffis
2007-03-13 19:39 ` Alexander Viro
2007-03-14 15:57 ` Amy Griffis [this message]
2007-03-14 3:06 ` 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=20070314155700.GA27762@fc.hp.com \
--to=amy.griffis@hp.com \
--cc=aviro@redhat.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--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