From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov
Subject: Re: [PATCH 0/6] SELinux UNIX domain socket fixes/cleanup
Date: Mon, 21 Jun 2010 15:13:17 -0400 [thread overview]
Message-ID: <201006211513.17495.paul.moore@hp.com> (raw)
In-Reply-To: <201006211432.53781.paul.moore@hp.com>
On Monday, June 21, 2010 02:32:53 pm Paul Moore wrote:
> On Saturday, May 29, 2010 05:53:16 pm Paul Moore wrote:
> > I finally got a chance to cobble together some tests to verify both
> > getpeercon() on the client end of a connected UNIX domain socket as well
> > as the proper operation of fsetxattr() on sockets. I'm happy to report
> > that everything worked as I expected it to (UNIX sockets now behave like
> > INET sockets) and nothing exploded. This latest version of the patchset
> > should include all the feedback I've received so far as well as my
> > sign-off on each patch so I think we should be in good shape at this
> > point. As a result, I'm submitting these patches for whatever kernel
> > release looks most appropriate - maybe to late for .35, but you might
> > be able to make a weak argument that some of the patches are
> > bugfixes - regardless, I'll let you guys make that call; as long as
> > they go somewhere I'll be happy.
> >
> > For those of you using git, you can also find a copy of the patches at
> > the URL below.
> >
> > * git://git.infradead.org/users/pcmoore/lblnet-2.6_testing
>
> Just a quick follow-up for the archives ... James has merged patches 2
> through 6 with patch 1 being intentionally excluded due to concerns from
> Stephan Smalley over the potential race conditions described in the
> comments.
My apologies, that would be _Stephen_ Smalley and not his evil twin Stephan ;)
--
paul moore
linux @ hp
--
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.
prev parent reply other threads:[~2010-06-21 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 21:53 [PATCH 0/6] SELinux UNIX domain socket fixes/cleanup Paul Moore
2010-05-29 21:53 ` [PATCH 1/6] selinux: Update socket's label alongside inode's label Paul Moore
2010-05-29 21:53 ` [PATCH 2/6] selinux: Set the peer label correctly on connected UNIX domain sockets Paul Moore
2010-05-29 21:53 ` [PATCH 3/6] selinux: Consolidate sockcreate_sid logic Paul Moore
2010-05-29 21:53 ` [PATCH 4/6] selinux: Shuffle the sk_security_struct alloc and free routines Paul Moore
2010-05-29 21:53 ` [PATCH 5/6] selinux: Convert socket related access controls to use socket labels Paul Moore
2010-05-29 21:53 ` [PATCH 6/6] selinux: Use current_security() when possible Paul Moore
2010-06-03 20:52 ` [PATCH 0/6] SELinux UNIX domain socket fixes/cleanup Paul Moore
2010-06-03 21:12 ` Eric Paris
2010-06-03 21:44 ` Paul Moore
2010-06-09 21:39 ` Paul Moore
2010-06-21 18:32 ` Paul Moore
2010-06-21 19:13 ` 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=201006211513.17495.paul.moore@hp.com \
--to=paul.moore@hp.com \
--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.