From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: Chris PeBenito <cpebenito@tresys.com>
Cc: selinux@tycho.nsa.gov
Subject: redhat1 polcap (was Re: [PATCH 1/1] Add SELinux policy capability for always checking packet and peer classes.)
Date: Fri, 3 May 2013 20:11:40 +0200 [thread overview]
Message-ID: <20130503181140.GC22935@siphos.be> (raw)
In-Reply-To: <1367586339-12509-1-git-send-email-cpebenito@tresys.com>
On Fri, May 03, 2013 at 09:05:39AM -0400, Chris PeBenito wrote:
[...]
> Includes definition of "redhat1" SELinux policy capability, which
> exists in the SELinux userpace library, to keep ordering correct.
>
> The SELinux userpace portion of this was merged last year, but this kernel
> change fell on the floor.
Would it make sense to rename the "redhat1" capability as "ptrace_child" or
so? The name "redhat1" seems quite different from the other ones
(network_peer_controls, open_perms, always_check_network).
Also, what is that about?
Wkr,
Sven Vermeulen
--
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:[~2013-05-03 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 13:05 [PATCH 1/1] Add SELinux policy capability for always checking packet and peer classes Chris PeBenito
2013-05-03 18:11 ` Sven Vermeulen [this message]
2013-05-06 13:55 ` redhat1 polcap (was Re: [PATCH 1/1] Add SELinux policy capability for always checking packet and peer classes.) Christopher J. PeBenito
2013-05-06 18:43 ` Sven Vermeulen
2013-05-03 21:24 ` [PATCH 1/1] Add SELinux policy capability for always checking packet and peer classes Paul Moore
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=20130503181140.GC22935@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=cpebenito@tresys.com \
--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.