From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, cpebenito@tresys.com,
vyekkirala@TrustedCS.com, jmorris@namei.org
Subject: Re: Q: SECMARK controls on forwarded packets
Date: Wed, 9 Jan 2008 10:36:21 -0500 [thread overview]
Message-ID: <200801091036.22078.paul.moore@hp.com> (raw)
In-Reply-To: <1199885981.9393.240.camel@moss-spartans.epoch.ncsc.mil>
On Wednesday 09 January 2008 8:39:41 am Stephen Smalley wrote:
> On Wed, 2008-01-09 at 08:30 -0500, Paul Moore wrote:
> > Fair enough. I'll try to think of something catchy to replace the
> > send permission in the forwarding outbound case ... if anybody has
> > any great ideas I'd love to hear them.
>
> Well, you could just go with the obvious:
> # inbound traffic to be forwarded
> allow peer_t secmark_t:packet forward_in;
> # outbound forwarded traffic
> allow peer_t secmark_t:packet forward_out;
'forward_in' and 'forward_out'? I thought I said "something catchy"?
:)
Seriously though, I can't think of anything better so { forward_in
forward_out } it is.
--
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:[~2008-01-09 15:36 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 [this message]
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
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=200801091036.22078.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=cpebenito@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.