From: Stephen Hemminger <shemminger@linux-foundation.org>
To: linux-security-module@vger.kernel.org
Cc: Al Viro <viro@ZenIV.linux.org.uk>, netdev@vger.kernel.org
Subject: Real networking namespace
Date: Fri, 9 Oct 2009 08:38:07 -0700 [thread overview]
Message-ID: <20091009083807.16e55b08@nehalam> (raw)
The existing networking namespace model is unattractive for what I want,
has anyone investigated better alternatives?
I would like to be able to allow access to a network interface and associated objects
(routing tables etc), to be controlled by Mandatory Access Control API's.
I.e grant access to eth0 and to only certain processes. Some the issues
with the existing models are:
* eth0 and associated objects don't really exist in filesystem so
not subject to LSM style control (SeLinux/SMACK/TOMOYO)
* network namespaces do not allow object to exist in multiple namespaces.
The current model is more restrictive than chroot jails. At least with
chroot, put filesystem objects in multiple jails.
Since one of the first rules of security is "don't reinvent", surely
others have dealt with this issue. Any good ideas?
next reply other threads:[~2009-10-09 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 15:38 Stephen Hemminger [this message]
2009-10-09 16:37 ` Real networking namespace Stephen Smalley
2009-10-09 16:44 ` Stephen Smalley
2009-10-09 22:12 ` Paul Moore
2009-10-10 2:08 ` Stephen Hemminger
2009-10-10 21:40 ` Paul Moore
2009-10-10 18:14 ` Casey Schaufler
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=20091009083807.16e55b08@nehalam \
--to=shemminger@linux-foundation.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).