From: Paul Moore <pmoore@redhat.com>
To: linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov,
eparis@redhat.com
Cc: netdev@vger.kernel.org, jasowang@redhat.com, mst@redhat.com
Subject: Re: [RFC PATCH v3 0/2] Fix some multiqueue TUN problems
Date: Wed, 19 Dec 2012 11:59:49 -0500 [thread overview]
Message-ID: <2198139.EQv1ADVakk@sifl> (raw)
In-Reply-To: <20121218225001.16104.34454.stgit@localhost>
On Tuesday, December 18, 2012 05:53:37 PM Paul Moore wrote:
> A refresh/respin of the LSM/SELinux fixes to work on top of Jason's
> latest API tweak (now living in DaveM's net tree). In general, I
> believe the hooks and thinking behind the v2 patchset still make sense
> so no changes there, although I did change the SELinux permission from
> "create_queue" to "attach_queue" to match the API changes.
>
> Comments are welcome and encouraged; we need to get this fixed before
> 3.8 is released.
SELinux (I'm looking at you Eric) and LSM folks - any comments/objections to
these changes?
> ---
>
> Paul Moore (2):
> selinux: add the "attach_queue" permission to the "tun_socket" class
> tun: fix LSM/SELinux labeling of tun/tap devices
--
paul moore
security and virtualization @ redhat
--
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:[~2012-12-19 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 22:53 [RFC PATCH v3 0/2] Fix some multiqueue TUN problems Paul Moore
2012-12-18 22:53 ` [RFC PATCH v3 1/2] selinux: add the "attach_queue" permission to the "tun_socket" class Paul Moore
2012-12-18 22:53 ` [RFC PATCH v3 2/2] tun: fix LSM/SELinux labeling of tun/tap devices Paul Moore
[not found] ` <20121218230808.GC1135@redhat.com>
[not found] ` <50D154B1.4010909@redhat.com>
2012-12-19 16:58 ` Paul Moore
2012-12-20 21:58 ` Eric Paris
2012-12-19 16:59 ` 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=2198139.EQv1ADVakk@sifl \
--to=pmoore@redhat.com \
--cc=eparis@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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.