From: Joy Latten <latten@austin.ibm.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: redhat-lspp@redhat.com, linux-audit@redhat.com
Subject: Re: [redhat-lspp] auditing labeled ipsec
Date: Fri, 13 Oct 2006 16:34:18 -0500 [thread overview]
Message-ID: <1160775258.17737.100.camel@faith.austin.ibm.com> (raw)
In-Reply-To: <200610121024.05288.sgrubb@redhat.com>
On Thu, 2006-10-12 at 10:24 -0400, Steve Grubb wrote:
> 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.
>
pfkey doesn't appear to use a queue like netlink... it registers socket
protocol operations such as .recvmsg and .sendmsg which get called via
sock_recvmsg and sock_sendmsg.
Joy
prev parent reply other threads:[~2006-10-13 21:34 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
2006-10-13 21:34 ` Joy Latten [this message]
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=1160775258.17737.100.camel@faith.austin.ibm.com \
--to=latten@austin.ibm.com \
--cc=linux-audit@redhat.com \
--cc=redhat-lspp@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox