From: Paul Moore <paul.moore@hp.com>
To: Pat Kane <pekane52@gmail.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Eric Paris <eparis@redhat.com>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
cxzhang@watson.ibm.com, sds@tycho.nsa.gov, jmorris@namei.org,
eparis@parisplace.org,
LSM <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH v2] net/unix: Add secdata to unix_stream msgs
Date: Wed, 23 Mar 2011 18:16:46 -0400 [thread overview]
Message-ID: <201103231816.46266.paul.moore@hp.com> (raw)
In-Reply-To: <AANLkTik55CAKfU5v4PE87h26vwAMy8vV7rhMmu9EA19B@mail.gmail.com>
On Wednesday, March 23, 2011 4:23:35 PM Pat Kane wrote:
> >> On Tue, 2011-03-22 at 19:32 -0700, David Miller wrote:
> >>> The SELINUX hook implementations even have "_dgram()" in their names.
>
> The LSM hook that I am having problems with, and that the patch fixes
> is "secid_to_secctx()" not "socket_getpeersec_dgram()".
Can you explain the problem you are having? I'm specifically interested in
who is calling secid_to_secctx() on a AF_UNIX stream packet.
Adding the secid token to a AF_UNIX stream packet isn't likely to be the right
solution, although until we hear what the core problem is, I'm not sure we can
offer any fixes.
--
paul moore
linux @ hp
prev parent reply other threads:[~2011-03-23 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 0:38 [PATCH v2] net/unix: Add secdata to unix_stream msgs Pat Kane
2011-03-23 2:32 ` David Miller
2011-03-23 15:57 ` Eric Paris
2011-03-23 16:11 ` Casey Schaufler
2011-03-23 20:23 ` Pat Kane
2011-03-23 22:16 ` Paul Moore [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=201103231816.46266.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=casey@schaufler-ca.com \
--cc=cxzhang@watson.ibm.com \
--cc=davem@davemloft.net \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekane52@gmail.com \
--cc=sds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).