From: "Venkat Yekkirala" <vyekkirala@trustedcs.com>
To: "'James Morris'" <jmorris@namei.org>,
"Paul Moore" <paul.moore@hp.com>,
"David S. Miller" <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <selinux@tycho.nsa.gov>,
"Venkat Yekkirala" <vyekkirala@tcsfw4.tcs-sec.com>,
"Stephen Smalley" <sds@tycho.nsa.gov>,
"Eric Paris" <eparis@redhat.com>
Subject: RE: [PATCH 00/11] The _entire_ secid reconciliation patchset (tada!)
Date: Wed, 11 Oct 2006 14:20:07 -0500 [thread overview]
Message-ID: <001101c6ed6a$43ae71e0$cc0a010a@tcssec.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610091612140.31187@d.namei>
> From an initial review of this patchset, it doesn't look
> quite ready to
> queue for 2.6.20 (which I plan to to via git once it is).
>
> Outstanding items include resolving the igmp skb hook issue
> generally,
> testing to verify both the design and implementation, and
> ensuring that
> all the related policy changes are merged upstream first.
>
Regarding the igmp hook issue, we could do a generic hook
like Paul suggested. Would that be more palatable you think?
next prev parent reply other threads:[~2006-10-11 19:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 19:42 [PATCH 00/11] The _entire_ secid reconciliation patchset (tada!) paul.moore
2006-10-09 19:42 ` [PATCH 01/11] secid reconciliation: new SELinux flask definitions paul.moore
2006-10-09 19:42 ` [PATCH 02/11] secid reconciliation: Add LSM hooks paul.moore
2006-10-09 19:42 ` [PATCH 03/11] secid reconciliation: Invoke LSM hook for inbound traffic paul.moore
2006-10-09 19:42 ` [PATCH 04/11] secid reconciliation: Invoke LSM hook for outbound traffic paul.moore
2006-10-09 19:42 ` [PATCH 05/11] secid reconciliation: Label locally generated IPv6 traffic paul.moore
2006-10-09 19:42 ` [PATCH 06/11] secid reconciliation: Label locally generated IPv4 traffic paul.moore
2006-10-09 19:42 ` [PATCH 07/11] secid reconciliation: Enforcement for SELinux paul.moore
2006-10-09 19:42 ` [PATCH 08/11] secid reconciliation: Use secmark when classifying flow using skb paul.moore
2006-10-09 19:42 ` [PATCH 09/11] secid reconciliation: Track peersecid at connection establishment paul.moore
2006-10-09 19:42 ` [PATCH 10/11] secid reconciliation: various fixes paul.moore
2006-10-09 19:42 ` [PATCH 11/11] secid reconciliation: support for NetLabel paul.moore
2006-10-09 20:19 ` [PATCH 00/11] The _entire_ secid reconciliation patchset (tada!) James Morris
2006-10-09 20:30 ` Paul Moore
2006-10-09 20:36 ` James Morris
2006-10-11 19:20 ` Venkat Yekkirala [this message]
2006-10-12 7:26 ` 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='001101c6ed6a$43ae71e0$cc0a010a@tcssec.com' \
--to=vyekkirala@trustedcs.com \
--cc=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--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 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).