From: Paul Moore <paul.moore@hp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: The art of breaking userspace (was Re: [GIT] SELinux changes for 2.6.23 (updated))
Date: Fri, 13 Jul 2007 23:20:39 -0400 [thread overview]
Message-ID: <200707132320.40024.paul.moore@hp.com> (raw)
In-Reply-To: <1184354963.3392.394.camel@moss-spartans.epoch.ncsc.mil>
On Friday, July 13 2007 3:29:23 pm Stephen Smalley wrote:
> Agreed, it needs to be fixed in the netlabel code.
For anyone interested, and for the sake of completeness, an updated patch[set]
has been posted to the SELinux mailing list for review. The new patchset is
designed to fix the problem that Michal reported.
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2007-07-14 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 10:41 [GIT] SELinux changes for 2.6.23 (updated) Paul Moore
2007-07-13 19:08 ` The art of breaking userspace (was Re: [GIT] SELinux changes for 2.6.23 (updated)) Michal Piotrowski
2007-07-13 19:29 ` Stephen Smalley
2007-07-14 3:20 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-13 19:39 Paul Moore
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=200707132320.40024.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=linux-kernel@vger.kernel.org \
/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