From: Joshua Brindle <jbrindle@tresys.com>
To: Venkat Yekkirala <vyekkirala@TrustedCS.com>
Cc: dwalsh@redhat.com, selinux@tycho.nsa.gov
Subject: Re: ipsec, netlabels, secmark- How about a little usability?
Date: Tue, 19 Sep 2006 21:35:26 -0400 [thread overview]
Message-ID: <45109ADE.8080402@tresys.com> (raw)
In-Reply-To: <36282A1733C57546BE392885C0618592015730E5@chaos.tcs.tcs-sec.com>
Venkat Yekkirala wrote:
>> We have been having some meetings to discuss how we can use
>> this stuff
>> in the real world (IE Non MLS), and I think the current
>> implementation
>> is coming up short. The discussions I have seen have talked
>> about using
>> getpeercon to look at the other end of the connections, but
>> this is not
>> in the spirit of SELinux where modification of the
>> applications should
>> not be necessary to secure the environment.
>>
>>
>
>
> So, what happens if an externally labeled packet (e.g.: Labeled IPSec)
> comes in thru the above entry point? First of all, a check is made to
> see if a packet so labeled using IPSec (unlabeled if no IPSec) can
> "flow in" thru the "entry point". If it can, and if there's an
> IPSec label on the packet, a transition sid is computed between the
> "entry point" label and the IPSec label and the packet will be marked
> with this transition sid. The transition label will either be the IPSec
> label (default) or any other label as defined by SELinux policy transition
> rules.
>
>
What if there are 2 external labels (ipsec and cipso) ?
--
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-09-20 1:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 21:19 ipsec, netlabels, secmark- How about a little usability? Venkat Yekkirala
2006-09-20 1:35 ` Joshua Brindle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-20 13:02 Venkat Yekkirala
2006-09-14 22:52 Venkat Yekkirala
2006-09-15 9:00 ` Stuart James
2006-09-14 14:52 Stuart James
2006-09-14 12:52 Daniel J Walsh
2006-09-14 13:50 ` Joshua Brindle
2006-09-14 13:55 ` Joshua Brindle
2006-09-14 14:43 ` Stephen Smalley
2006-09-15 15:36 ` Daniel J Walsh
2006-09-14 16:02 ` James Antill
2006-09-14 16:49 ` Stephen Smalley
2006-09-14 17:24 ` James Antill
2006-09-14 19:45 ` Stephen Smalley
2006-09-19 20:13 ` Karl MacMillan
2006-09-19 20:35 ` Christopher J. PeBenito
2006-09-19 21:12 ` Karl MacMillan
2006-09-19 20:47 ` Karl MacMillan
2006-09-20 13:30 ` Christopher J. PeBenito
2006-09-20 13:45 ` James Morris
2006-09-20 14:27 ` Christopher J. PeBenito
2006-09-20 14:45 ` 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=45109ADE.8080402@tresys.com \
--to=jbrindle@tresys.com \
--cc=dwalsh@redhat.com \
--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.