From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <paul.moore@hp.com>
Cc: redhat-lspp@redhat.com, linux-audit@redhat.com
Subject: Re: [redhat-lspp] auditing labeled ipsec
Date: Thu, 12 Oct 2006 10:24:05 -0400 [thread overview]
Message-ID: <200610121024.05288.sgrubb@redhat.com> (raw)
In-Reply-To: <452E4E2B.1030101@hp.com>
On Thursday 12 October 2006 10:16, Paul Moore wrote:
> PF_KEYv2 is a socket family/protocol defined by RFC2367 whose original goal
> was to standardize the interface between the in-kernel IPsec bits and the
> userland key management daemon.
OK, then the question becomes is the communication protocol asyncronous or
synchronous? If synchronous (the request is handled immediately and not
queued like netlink), then current task struct can be used. Otherwise, there
may be some more code needed to grab the loginuid during the send and store
it with the packet until dequeued. If it is async, there may be selinux
implications as well.
-Steve
next prev parent reply other threads:[~2006-10-12 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 20:40 auditing labeled ipsec Joy Latten
2006-10-11 20:58 ` Paul Moore
2006-10-11 21:43 ` [redhat-lspp] " Joy Latten
2006-10-11 22:23 ` Klaus Weidner
2006-10-12 12:36 ` [redhat-lspp] " Steve Grubb
2006-10-12 14:16 ` Paul Moore
2006-10-12 14:24 ` Steve Grubb [this message]
2006-10-13 21:34 ` Joy Latten
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=200610121024.05288.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul.moore@hp.com \
--cc=redhat-lspp@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