From: "Timothy R. Chavez" <tinytim@us.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: James Morris <jmorris@redhat.com>,
selinux@tycho.nsa.gov,
Linux Audit Discussion <linux-audit@redhat.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [RFC][PATCH] collect security labels on user processes generating audit messages
Date: Thu, 09 Feb 2006 11:39:47 -0600 [thread overview]
Message-ID: <1139506788.10222.29.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0602091155340.780@excalibur.intercode>
On Thu, 2006-02-09 at 12:03 -0500, James Morris wrote:
<snip>
> > > security_task_getsid() doesn't exist.
> > >
> > > You created security_task_getsecurity(), which retrieves the security
> > > context.
> >
> > Actually, security_task_getsid() does exist (or did exist last time I
> > updated the viro/audit-2.6 git tree).
> >
> > http://www.promethos.org/lxr/http/ident?i=security_task_getsid
>
> Oh, ok.
>
> Where is security_task_getsecurity() used, then?
>
>
> - James
Hm... :) I made it at first because I was just going to extract the
context directly and store it with the skb_params, but then decided to
go the 'sid' route. I left it in to expand the LSM API a little, but if
it's not being used currently, it probably shouldn't be included, eh?
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-09 17:39 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 [this message]
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
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=1139506788.10222.29.camel@localhost \
--to=tinytim@us.ibm.com \
--cc=jmorris@namei.org \
--cc=jmorris@redhat.com \
--cc=linux-audit@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.