From: Chris PeBenito <pebenito@ieee.org>
To: Russell Coker <russell@coker.com.au>, selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] puppet patch V2
Date: Thu, 17 Feb 2022 08:49:53 -0500 [thread overview]
Message-ID: <2dce0336-6e94-4ae2-6f9e-a1257962b20e@ieee.org> (raw)
In-Reply-To: <3266491.hCnaqv1u2z@liv>
On 2/16/22 20:41, Russell Coker wrote:
> On Thursday, 17 February 2022 02:30:12 AEDT Chris PeBenito wrote:
>> On 2/16/2022 08:08, Russell Coker wrote:
>>> On Wednesday, 16 February 2022 22:35:58 AEDT Chris PeBenito wrote:
>>>> Why are you adding bin_t as an entrypoint here and below?
>>>
>>> That's for running a script via the interpreter instead of via a
>>> #!/usr/bin/ whatever so you can't just label the script file.
>>
>> I'm not sure I follow. Are you saying this is for handling things like
>> "bash -c /some/script" and "python foo.py"?
>
> Yes.
I don't think we make this type of accomodation elsewhere in the policy, so I'm
inclined to say no to this part of the change.
--
Chris PeBenito
prev parent reply other threads:[~2022-02-17 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 1:57 [PATCH] puppet patch V2 Russell Coker
2022-02-16 11:35 ` Chris PeBenito
2022-02-16 13:08 ` Russell Coker
2022-02-16 15:30 ` Chris PeBenito
2022-02-17 1:41 ` Russell Coker
2022-02-17 13:49 ` Chris PeBenito [this message]
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=2dce0336-6e94-4ae2-6f9e-a1257962b20e@ieee.org \
--to=pebenito@ieee.org \
--cc=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).