From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Venkat Yekkirala <vyekkirala@TrustedCS.com>,
jbrindle@tresys.com, selinux@tycho.nsa.gov,
Stephen Smalley <sds@tycho.nsa.gov>,
gcwilson@us.ibm.com
Subject: Re: SELinux Networking Enhancements
Date: Wed, 01 Nov 2006 11:09:59 -0500 [thread overview]
Message-ID: <4548C6D7.1050709@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611011059190.6253@d.namei>
James Morris wrote:
> On Wed, 1 Nov 2006, Paul Moore wrote:
>
>>>Ok, so, there'd be an iptables match which looked up the security context
>>>on the SA the packet arrives/departs on? Sounds like it could work.
>>>Perhaps call it xfrmlabel ?
>>
>>What we name it probably isn't that important, but I sorta prefer Venkat's
>>original suggestion of secfilter (or secidfilter, or <generic security
>>token>filter) since it sounds like this new component would be strictly for
>>filtering and not labeling.
>
> Well, it's matching labels on xfrms. The filtering concept is implicit in
> it being an iptables match, and secid/sec is vague.
I got the impression that Venkat was intending this to work for external labels
(both XFRM and NetLabel) as well as internal labels (SECMARK). I would be a lot
happier if the name didn't limit it to just XFRM labeling.
--
paul moore
linux security @ hp
--
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:[~2006-11-01 16:09 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 15:10 SELinux Networking Enhancements Venkat Yekkirala
2006-10-20 23:24 ` James Morris
2006-10-23 16:32 ` Venkat Yekkirala
2006-10-23 21:17 ` James Morris
2006-10-24 14:33 ` Venkat Yekkirala
2006-10-30 18:27 ` James Morris
2006-10-30 18:34 ` Joshua Brindle
2006-10-30 18:40 ` James Morris
2006-10-30 18:43 ` Joshua Brindle
2006-10-30 18:49 ` James Morris
2006-10-31 20:54 ` Venkat Yekkirala
2006-11-01 3:46 ` James Morris
2006-11-01 15:04 ` Paul Moore
2006-11-01 16:00 ` James Morris
2006-11-01 16:09 ` Paul Moore [this message]
2006-11-01 17:26 ` James Morris
2006-11-01 17:39 ` Paul Moore
2006-11-01 20:59 ` Venkat Yekkirala
2006-11-01 21:29 ` Paul Moore
2006-11-02 15:15 ` Venkat Yekkirala
2006-11-02 15:26 ` Paul Moore
2006-11-02 15:47 ` Venkat Yekkirala
2006-11-02 16:43 ` James Morris
2006-11-02 16:45 ` James Morris
2006-11-02 17:10 ` Venkat Yekkirala
2006-11-02 17:22 ` James Morris
2006-11-02 17:31 ` Venkat Yekkirala
2006-11-02 16:49 ` Joshua Brindle
2006-11-02 17:01 ` Venkat Yekkirala
2006-11-02 17:19 ` Joshua Brindle
2006-11-02 17:38 ` Venkat Yekkirala
2006-11-02 17:51 ` Paul Moore
2006-11-02 17:53 ` Joshua Brindle
2006-11-03 15:12 ` Venkat Yekkirala
2006-11-03 18:44 ` Joshua Brindle
2006-11-01 14:02 ` Christopher J. PeBenito
2006-11-01 15:58 ` Venkat Yekkirala
2006-11-01 17:54 ` Joshua Brindle
2006-11-01 17:59 ` Paul Moore
2006-11-01 19:25 ` Venkat Yekkirala
2006-11-01 19:46 ` Joshua Brindle
2006-11-01 17:55 ` Christopher J. PeBenito
2006-11-01 18:30 ` Paul Moore
2006-11-01 19:57 ` James Morris
2006-11-01 19:59 ` Joshua Brindle
2006-11-02 16:20 ` Venkat Yekkirala
2006-11-02 18:33 ` Christopher J. PeBenito
2006-11-03 14:49 ` Venkat Yekkirala
[not found] <36282A1733C57546BE392885C06185920166D6EC@chaos.tcs.tcs-sec.com>
2006-11-02 16:22 ` Venkat Yekkirala
2006-11-02 16:31 ` Joshua Brindle
2006-11-02 16:54 ` Venkat Yekkirala
-- strict thread matches above, loose matches on Subject: below --
2006-10-16 14:55 Venkat Yekkirala
2006-10-16 3:14 Venkat Yekkirala
2006-10-16 12:40 ` Joshua Brindle
2006-10-16 14:31 ` Venkat Yekkirala
2006-10-18 13:23 ` Joshua Brindle
2006-10-18 14:08 ` Joe Nall
2006-10-18 15:10 ` Venkat Yekkirala
2006-10-18 16:09 ` Joshua Brindle
2006-10-19 15:06 ` Venkat Yekkirala
2006-10-19 16:04 ` Joshua Brindle
2006-10-19 16:54 ` Venkat Yekkirala
2006-10-19 21:27 ` James Morris
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=4548C6D7.1050709@hp.com \
--to=paul.moore@hp.com \
--cc=gcwilson@us.ibm.com \
--cc=jbrindle@tresys.com \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.com \
/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.