From: Russell Coker <russell@coker.com.au>
To: Paul Moore <paul.moore@hp.com>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>, "SE-Linux" <selinux@tycho.nsa.gov>
Subject: Re: tun/tap and SE Linux in 2.6.32
Date: Thu, 10 Dec 2009 07:56:22 +1100 [thread overview]
Message-ID: <200912100756.24553.russell@coker.com.au> (raw)
In-Reply-To: <200912091548.03369.paul.moore@hp.com>
On Thu, 10 Dec 2009, Paul Moore <paul.moore@hp.com> wrote:
> > Subject: selinux PERMISSIVE blocking tun/tap device creation in v2.6.32
>
> I imagine this is because the original reporter is using a SELinux policy
> without the new TUN socket classes/permissions (which is likely the common
> case at this point). The unknown class/permission handling that Eric added
> _should_ protect us from this - Russel do you have any more information
> about the distribution and policy in use here?
Sorry, the original message apparently wasn't clear enough (I've added some
caps).
The problem occurred in permissive mode. When the system is in permissive
mode then SE Linux should not deny any action that Unix permissions will
permit.
--
russell@coker.com.au
http://etbe.coker.com.au/ My Main Blog
http://doc.coker.com.au/ My Documents Blog
--
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.
next prev parent reply other threads:[~2009-12-09 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 1:32 tun/tap and SE Linux in 2.6.32 Russell Coker
2009-12-09 20:48 ` Paul Moore
2009-12-09 20:56 ` Russell Coker [this message]
2009-12-09 21:26 ` Stephen Smalley
2009-12-09 21:45 ` 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=200912100756.24553.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=paul.moore@hp.com \
--cc=sds@epoch.ncsc.mil \
--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.