From: "Venkat Yekkirala" <vyekkirala@TrustedCS.com>
To: "Venkat Yekkirala" <vyekkirala@tcsfw4.tcs-sec.com>,
"'Christopher J. PeBenito'" <cpebenito@tresys.com>
Cc: <selinux@tycho.nsa.gov>, <redhat-lspp@redhat.com>
Subject: RE: DOCUMENTATION OF SECID RECONCILIATION AND FLOW CONTROL FOR POLICY WRITERS
Date: Fri, 13 Oct 2006 19:03:29 -0500 [thread overview]
Message-ID: <001801c6ef24$2f2edfa0$cc0a010a@tcssec.com> (raw)
In-Reply-To:
> > turns into:
> >
> > allow unlabeled_t network_t:packet flow_in;
>
> as it happens currently.
>
> > allow unconfined_t unlabeled_t:packet flow_in;
>
> as it happens currently.
Well, as: allow unconfined_t unlabeled_t:packet recv;
>
> > allow unconfined_t unlabeled_t:packet flow_out;
>
> Not needed since we have a check against network_t
> as mentioned next.
>
> > allow unlabeled_t network_t:packet flow_out;
> >
> > which seems more correct to me and is clearer and more consistent.
>
> which, after all said and done is what in fact is (should be)
> happening.
>
> But the fights in the earlier part still hold true, which
> makes me wonder
> where did you/I get off the track?
>
--
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 reply other threads:[~2006-10-14 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 0:03 Venkat Yekkirala [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 12:24 DOCUMENTATION OF SECID RECONCILIATION AND FLOW CONTROL FOR POLICY WRITERS Venkat Yekkirala
2006-10-09 19:26 ` Venkat Yekkirala
2006-10-13 23:23 ` Venkat Yekkirala
2006-10-13 20:55 ` Christopher J. PeBenito
2006-10-13 23:58 ` Venkat Yekkirala
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='001801c6ef24$2f2edfa0$cc0a010a@tcssec.com' \
--to=vyekkirala@trustedcs.com \
--cc=cpebenito@tresys.com \
--cc=redhat-lspp@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@tcsfw4.tcs-sec.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.