From: "Timothy R. Chavez" <tinytim@us.ibm.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
linux-audit@redhat.com, selinux@tycho.nsa.gov,
James Morris <jmorris@namei.org>
Subject: Re: [RFC][PATCH] collect security labels on user processes generating audit messages
Date: Thu, 16 Feb 2006 10:27:58 -0600 [thread overview]
Message-ID: <1140107279.7961.1.camel@localhost> (raw)
In-Reply-To: <200602161035.15321.sgrubb@redhat.com>
On Thu, 2006-02-16 at 10:35 -0500, Steve Grubb wrote:
> On Thursday 16 February 2006 10:29, Stephen Smalley wrote:
> > Except for what other code should do about NULL pointers in output. If
> > they defer it to vsnprintf, they will end up with <NULL> in the output.
> > So should Tim's code be checking for !ctx and outputting (null) there as
> > well?
>
> Yes, I think that would be consistent will all the other audit code.
>
> -Steve
>
Yes. I've already made this change. I just saw that Darren's recent
patch submission included the API work I just did (that he suggested
yesterday)... in the process of testing now.
Thanks.
-tim
--
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:[~2006-02-16 16:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 1:32 [RFC][PATCH] collect security labels on user processes generating audit messages Timothy R. Chavez
2006-02-09 14:58 ` James Morris
2006-02-09 15:10 ` Darrel Goeddel
2006-02-09 15:15 ` James Morris
2006-02-09 17:43 ` Stephen Smalley
2006-02-09 16:13 ` Timothy R. Chavez
2006-02-09 17:03 ` James Morris
2006-02-09 17:39 ` Timothy R. Chavez
2006-02-09 17:29 ` Stephen Smalley
2006-02-09 18:13 ` Stephen Smalley
2006-02-10 0:14 ` Timothy R. Chavez
2006-02-10 4:00 ` James Morris
2006-02-13 19:12 ` Stephen Smalley
2006-02-14 23:48 ` Timothy R. Chavez
2006-02-15 13:47 ` Stephen Smalley
2006-02-15 15:49 ` Timothy R. Chavez
2006-02-15 16:14 ` Linda Knippers
2006-02-15 16:22 ` Steve Grubb
2006-02-15 16:37 ` Stephen Smalley
2006-02-15 16:41 ` Steve Grubb
2006-02-15 16:58 ` Timothy R. Chavez
2006-02-15 18:33 ` Timothy R. Chavez
2006-02-15 17:17 ` Linda Knippers
2006-02-15 18:14 ` Steve Grubb
2006-02-15 18:20 ` Steve Grubb
2006-02-16 14:56 ` Steve Grubb
2006-02-16 15:29 ` Stephen Smalley
2006-02-16 15:35 ` Steve Grubb
2006-02-16 16:27 ` Timothy R. Chavez [this message]
2006-02-16 19:03 ` Lamont R. Peterson
2006-02-16 20:44 ` Timothy R. Chavez
2006-02-15 16:17 ` Stephen Smalley
2006-02-15 16:41 ` Timothy R. Chavez
2006-02-15 16:38 ` Stephen Smalley
2006-02-15 21:05 ` Darrel Goeddel
2006-02-17 20:58 ` Timothy R. Chavez
2006-02-22 14:21 ` Stephen Smalley
2006-02-22 17:14 ` Timothy R. Chavez
2006-02-22 14:26 ` Stephen Smalley
2006-02-22 17:13 ` Timothy R. Chavez
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=1140107279.7961.1.camel@localhost \
--to=tinytim@us.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-audit@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--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.