From: Paul Moore <paul@paul-moore.com>
To: SELinux@tycho.nsa.gov
Cc: Chris PeBenito <cpebenito@tresys.com>
Subject: Re: [PATCH 2/2] Update SELinux policy capability to always check peer class.
Date: Thu, 07 Jun 2012 10:28:59 -0400 [thread overview]
Message-ID: <16742766.tXTOYM7uO2@sifl> (raw)
In-Reply-To: <1339003731-6743-2-git-send-email-cpebenito@tresys.com>
On Wednesday, June 06, 2012 01:28:51 PM Chris PeBenito wrote:
> Update the always_check_network policy capability which, when enabled,
> treats peer labeling as enabled, even if there is no Netlabel or
> labeled IPSEC configuration.
>
> Signed-off-by: Chris PeBenito <cpebenito@tresys.com>
I still object to this patchset for all the same old reasons, but I feel
obligated to point out that this patchset is still incomplete/incorrect in
that it only deals with the socket_sock_rcv_skb hook.
--
paul moore
www.paul-moore.com
--
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 prev parent reply other threads:[~2012-06-07 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 17:28 [PATCH 1/2] Add SELinux policy capability for always checking packet class Chris PeBenito
2012-06-06 17:28 ` [PATCH 2/2] Update SELinux policy capability to always check peer class Chris PeBenito
2012-06-07 14:28 ` Paul Moore [this message]
2012-06-07 15:27 ` Christopher J. PeBenito
2012-06-07 15:33 ` Paul Moore
2012-06-07 16:08 ` Christopher J. PeBenito
2012-06-07 16:52 ` Paul Moore
2012-06-07 17:43 ` Eric Paris
-- strict thread matches above, loose matches on Subject: below --
2012-06-07 18:28 [PATCH 1/2] Add SELinux policy capability for always checking packet class Chris PeBenito
2012-06-07 18:28 ` [PATCH 2/2] Update SELinux policy capability to always check peer class Chris PeBenito
2012-06-08 17:36 ` Paul Moore
2012-06-08 18:29 ` Christopher J. PeBenito
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=16742766.tXTOYM7uO2@sifl \
--to=paul@paul-moore.com \
--cc=SELinux@tycho.nsa.gov \
--cc=cpebenito@tresys.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.