From: Venkat Yekkirala <vyekkirala@trustedcs.com>
To: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Cc: jmorris@namei.org, sds@tycho.nsa.gov, chanson@trustedcs.com
Subject: [PATCH 0/3] secid reconciliation-v01: Repost patchset with updates
Date: Thu, 24 Aug 2006 12:50:34 -0500 [thread overview]
Message-ID: <44EDE6EA.1090601@trustedcs.com> (raw)
The following are the changes included in this patchset since the previous post:
- Use SELinux transition rules instead of precedence when reconciling the secid's
making it flexible/policy-driven; xfrm secid would prevail by default.
- Change the naming of access vector perms to flow_in and flow_out.
- Make selinux_xfrm_sock_rcv_skb checks conditional on compat_net.
- Switch selinux_inet_conn_request to use secmark; cipso is still allowed to
override secmark currently in this regard (will rely on Paul Moore at HP
to bring cipso into the reconciliation path).
This patchset is relative to David Miller's net-2.6.19.git.
Please consider for inclusion in 2.6.19.
next reply other threads:[~2006-08-24 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 17:50 Venkat Yekkirala [this message]
2006-08-24 19:37 ` [PATCH 0/3] secid reconciliation-v01: Repost patchset with updates 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=44EDE6EA.1090601@trustedcs.com \
--to=vyekkirala@trustedcs.com \
--cc=chanson@trustedcs.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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).