From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
netdev@vger.kernel.org
Subject: [RFC PATCH v1 0/6] Labeled networking patches for 2.6.28
Date: Fri, 08 Aug 2008 16:52:45 -0400 [thread overview]
Message-ID: <20080808203542.21077.37084.stgit@flek> (raw)
Hello everyone,
Attached is a short series of patches which fixup some issues with labeled
networking and add an important new feature: NetLabel address selectors. The
addition of NetLabel address selectors is pretty cool because it now allows
you to toggle NetLabel based labeling by both the sending domain _and_ the
destination address. For example, if you were to configure the SELinux
ping_t domain to send CIPSO labeled packets every packet sent by the ping_t
domain would be labeled, including DNS requests (very annoying!).
# netlabelctl -p map list
Configured NetLabel domain mappings (2)
domain: "ping_t"
protocol: CIPSOv4, DOI = 1
domain: DEFAULT
protocol: UNLABELED
This addition of address selectors now allows you to breakdown the single
domain configuration by destination address. This allows you to specify
different labeling configuration within the ping_t domain.
# netlabelctl -p map list
Configured NetLabel domain mappings (2)
domain: "ping_t"
address: 192.168.0.78/32
protocol: CIPSOv4, DOI = 1
address: 0.0.0.0/0
protocol: UNLABELED
domain: DEFAULT
protocol: UNLABELED
In the example above, only packets sent to 192.168.0.78 from the ping_t
domain will be labeled with a CIPSO label; everything else, i.e. 0.0.0.0/0,
is unlabeled. You will also notice that the default mapping is still using
the traditional (one domain, one configuration) policy, this is because you
have the option to use the address selectors on a per-domain basis.
The patches below are still pretty rough, but they do work as a proof of
concept that functions without any regressions under simple testing. I
would ask that you give the patches a quick review and let me know if you
see anything scary; patch #4 in particular makes me nervous because of the
IP header manipulation. I'll send out instructions on how to configure
the new bits later but I wanted to get this out now so people could look
it over.
The patches are included in the lblnet-2.6_testing tree:
* git://git.infradead.org/users/pcmoore/lblnet-2.6_testing
The matching userspace changes can be found in the netlabel_tools
"addrsel" branch:
* http://netlabel.svn.sf.net/viewvc/netlabel/netlabel_tools/branches/addrsel
Thanks.
--
paul moore
linux @ hp
next reply other threads:[~2008-08-08 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 20:52 Paul Moore [this message]
2008-08-08 20:52 ` [RFC PATCH v1 1/6] selinux: Fix a problem in security_netlbl_sid_to_secattr() Paul Moore
2008-08-08 20:53 ` [RFC PATCH v1 2/6] netlabel: Replace protocol/NetLabel linking with refrerence counts Paul Moore
2008-08-08 22:37 ` Paul E. McKenney
2008-08-09 2:11 ` Paul Moore
2008-08-09 13:23 ` Paul E. McKenney
2008-08-09 14:40 ` Paul Moore
2008-08-08 20:53 ` [RFC PATCH v1 3/6] netlabel: Add a generic way to create ordered linked lists of network addrs Paul Moore
2008-08-08 20:53 ` [RFC PATCH v1 4/6] netlabel: Add network address selectors to the NetLabel/LSM domain mapping Paul Moore
2008-08-08 20:53 ` [RFC PATCH v1 5/6] netlabel: Add functionality to set the security attributes of a packet Paul Moore
2008-08-08 20:53 ` [RFC PATCH v1 6/6] selinux: Set socket NetLabel based on connection endpoint Paul Moore
2008-08-08 23:09 ` [RFC PATCH v1 0/6] Labeled networking patches for 2.6.28 David Miller
2008-08-09 2:18 ` 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=20080808203542.21077.37084.stgit@flek \
--to=paul.moore@hp.com \
--cc=linux-security-module@vger.kernel.org \
--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 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).