From: James Morris <jmorris@namei.org>
To: Venkat Yekkirala <vyekkirala@TrustedCS.com>
Cc: David Miller <davem@davemloft.net>,
paul.moore@hp.com, netdev@vger.kernel.org, selinux@tycho.nsa.gov,
sds@tycho.nsa.gov, eparis@redhat.com, johnpol@2ka.mipt.ru,
herbert@gondor.apana.org.au
Subject: RE: [PATCH 1/3] Fix for IPsec leakage with SELinux enabled - V.03
Date: Thu, 5 Oct 2006 19:05:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610051903500.26861@d.namei> (raw)
In-Reply-To: <36282A1733C57546BE392885C0618592015CFB65@chaos.tcs.tcs-sec.com>
On Thu, 5 Oct 2006, Venkat Yekkirala wrote:
> > We're trying to fill the flow cache here. In the case where we'd
> > have a match in both the sub-policy and main table, I think the
> > sub-policy is supposed to take precedence, and if you fail to get
> > this sub-policy you should fail the entire lookup.
>
> Which is what's happening here correct?
Yes, the patch is correct for this.
The way sub-policy is used is during Mobile IP, where you have multiple
policies composed, so it wouldn't make sense for one of the policies to be
rejected and the other allowed and for packets to flow.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2006-10-05 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 21:27 [PATCH 1/3] Fix for IPsec leakage with SELinux enabled - V.03 Venkat Yekkirala
2006-10-05 21:47 ` David Miller
2006-10-05 23:05 ` James Morris [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-05 21:17 Venkat Yekkirala
2006-10-05 23:30 ` James Morris
2006-10-05 20:42 Venkat Yekkirala
2006-10-05 20:54 ` James Morris
2006-10-05 21:04 ` David Miller
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=Pine.LNX.4.64.0610051903500.26861@d.namei \
--to=jmorris@namei.org \
--cc=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).