From: Paul Moore <pmoore@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org
Subject: [GIT PULL] SELinux fixes for 3.13
Date: Thu, 12 Dec 2013 17:32:50 -0500 [thread overview]
Message-ID: <2686888.TAheoMSe76@sifl> (raw)
Hi James,
Here are a few patches to fix problems in 3.13-rcX. One some memory leak fix
for patches introduced in 3.13 and four patches to resolve a long standing
issue with TCP SYN-ACKs. All of these patches have been part of linux-next
for at least a day and pass the SELinux testsuite without issue.
Enjoy,
-Paul
---
The following changes since commit 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52:
Linux 3.12 (2013-11-03 15:41:51 -0800)
are available in the git repository at:
git://git.infradead.org/users/pcmoore/selinux_fixes master
for you to fetch changes up to c0828e50485932b7e019df377a6b0a8d1ebd3080:
selinux: process labeled IPsec TCP SYN-ACK packets properly in
selinux_ip_postroute() (2013-12-12 17:21:31 -0500)
----------------------------------------------------------------
Geyslan G. Bem (1):
selinux: fix possible memory leak
Paul Moore (5):
Merge tag 'v3.12'
selinux: handle TCP SYN-ACK packets correctly in selinux_ip_output()
selinux: handle TCP SYN-ACK packets correctly in selinux_ip_postroute()
selinux: look for IPsec labels on both inbound and outbound packets
selinux: process labeled IPsec TCP SYN-ACK packets properly in
selinux_ip_postroute()
security/selinux/hooks.c | 137 +++++++++++++++++++++++++++++++-------
security/selinux/include/xfrm.h | 8 +-
security/selinux/xfrm.c | 62 ++++++++++++++----
3 files changed, 165 insertions(+), 42 deletions(-)
--
paul moore
security and virtualization @ redhat
--
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.
reply other threads:[~2013-12-12 22:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2686888.TAheoMSe76@sifl \
--to=pmoore@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--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 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.