From: pebenito@ieee.org (Chris PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] single binary modutils
Date: Sat, 6 Aug 2016 16:53:28 -0400 [thread overview]
Message-ID: <d2d99537-6013-1d98-ac0a-e4bab5b8e0d9@ieee.org> (raw)
In-Reply-To: <201608031233.21247.russell@coker.com.au>
On 08/02/16 22:33, Russell Coker wrote:
> On Wed, 3 Aug 2016 09:59:28 AM Chris PeBenito wrote:
>> On 07/31/16 08:34, Russell Coker wrote:
>>> The following patch deals with a single binary for modutils, so depmod_t,
>>> and insmod_t are merged.
>>
>> Since the main SELinux distros (including RHEL/CentOS 7) all have merged
>> modutils these days, I'm open to taking a patch that fully merges these
>> domains (in which case renaming to kmod_t, with proper aliasing seems
>> the best idea).
>
> OK.
>
>> However, it's been some time since I used a busybox-based system; does
>> busybox still have separated tools? Yes, this is a bit of an obvious
>> question since busybox is also single-binary, but IIRC, the embedded
>> guys made some tiny helper scripts or executables so proper
>> transitioning could occur. Separate domains may still make sense.
>
> Maybe have an ifdef(`embedded' or something around it then?
I'm having a hard time envisioning how that would work.
If anyone is using busybox like this, please speak up. No sense in us
trying to handle a use case that no one uses.
--
Chris PeBenito
next prev parent reply other threads:[~2016-08-06 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 12:34 [refpolicy] [PATCH] single binary modutils Russell Coker
2016-08-02 23:59 ` Chris PeBenito
2016-08-03 2:33 ` Russell Coker
2016-08-06 20:53 ` Chris PeBenito [this message]
2016-10-21 8:35 ` Russell Coker
2016-10-23 23:28 ` Chris 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=d2d99537-6013-1d98-ac0a-e4bab5b8e0d9@ieee.org \
--to=pebenito@ieee.org \
--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.