From: Joshua Brindle <jbrindle@tresys.com>
To: Paul Moore <paul.moore@hp.com>
Cc: Chad Hanson <chanson@TrustedCS.com>,
James Morris <jmorris@namei.org>,
selinux@tycho.nsa.gov, sds@tycho.nsa.gov, cpebenito@tresys.com,
Venkat Yekkirala <vyekkirala@TrustedCS.com>
Subject: Re: Q: SECMARK controls on forwarded packets
Date: Thu, 10 Jan 2008 13:56:32 -0500 [thread overview]
Message-ID: <47866A60.40002@tresys.com> (raw)
In-Reply-To: <200801101147.06142.paul.moore@hp.com>
Paul Moore wrote:
> On Thursday 10 January 2008 10:32:10 am Chad Hanson wrote:
>> These controls look good to us...
>
> Great. I'm assuming the lack of complaints means others are happy with
> this as well.
>
I haven't gotten around to looking at the rfc in detail but it looks
like the secmark/external labeling concepts are being merged again when
we already decided to keep them as separate systems. Is the claim here
that it isn't possible to do forwarding controls without interaction
between them?
--
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:[~2008-01-10 18:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 4:30 Q: SECMARK controls on forwarded packets Paul Moore
2008-01-09 12:51 ` Stephen Smalley
2008-01-09 13:30 ` Paul Moore
2008-01-09 13:39 ` Stephen Smalley
2008-01-09 15:36 ` Paul Moore
2008-01-09 14:04 ` James Morris
2008-01-09 20:48 ` Paul Moore
2008-01-09 23:35 ` Paul Moore
2008-01-10 15:32 ` Chad Hanson
2008-01-10 16:47 ` Paul Moore
2008-01-10 18:56 ` Joshua Brindle [this message]
2008-01-10 19:10 ` Paul Moore
2008-01-10 20:04 ` Joshua Brindle
2008-01-10 20:07 ` 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=47866A60.40002@tresys.com \
--to=jbrindle@tresys.com \
--cc=chanson@TrustedCS.com \
--cc=cpebenito@tresys.com \
--cc=jmorris@namei.org \
--cc=paul.moore@hp.com \
--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.