From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Likewise policy
Date: Mon, 08 Mar 2010 20:42:01 +0100 [thread overview]
Message-ID: <4B955309.5090006@gmail.com> (raw)
In-Reply-To: <4B955272.4040003@gmail.com>
On 03/08/2010 08:39 PM, Dominick Grift wrote:
> On 03/08/2010 08:12 PM, Scott Salley wrote:
>>>> +allow lwsmd_t lwregd_t:process { signal siginh rlimitinh };
>>>> +allow lwsmd_t netlogond_t:process { signal siginh rlimitinh };
>>>> +allow lwsmd_t srvsvcd_t:process { signal siginh rlimitinh };
>>
>>> I suspect these can be removed. signal is already allowed and the other
>>> permissions are rarely needed.
>>
>> Where is signal already allowed? (siginh and rlimitinh can certainly be removed).
>
> + allow $1 self:process { signal_perms getsched setsched };
>
> It is included in the signal_perms permission set. (likewise.if)
Whoops my bad. That is to self and yours is to other domain types.
skip that comment please.
>>
>> Thank you for all the comments/advice/criticism.
>> _______________________________________________
>> refpolicy mailing list
>> refpolicy at oss.tresys.com
>> http://oss.tresys.com/mailman/listinfo/refpolicy
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20100308/1450dd94/attachment.bin
next prev parent reply other threads:[~2010-03-08 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 19:12 [refpolicy] [PATCH 1/1] Likewise policy Scott Salley
2010-03-08 19:39 ` Dominick Grift
2010-03-08 19:42 ` Dominick Grift [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-06 2:05 Scott Salley
2010-03-06 9:32 ` Dominick Grift
2010-03-08 13:40 ` 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=4B955309.5090006@gmail.com \
--to=domg472@gmail.com \
--cc=refpolicy@oss.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.