On 08/05/2011 10:45 AM, Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/05/2011 10:18 AM, Stephen Smalley wrote:
>> On Thu, 2011-08-04 at 17:50 -0400, Daniel J Walsh wrote:
>>> On 08/04/2011 05:10 PM, Eric Paris wrote:
>>>> On 08/04/2011 05:06 PM, Daniel J Walsh wrote:
>>>>> On 08/04/2011 05:00 PM, Eric Paris wrote:
>>>>
>>>>>> I also question the use of /sys/fs/selinux/ but I'm not sure
>>>>>> we have a good way to find that in a script..... Do we have
>>>>>> one?
>>>>>>
>>>>>
>>>>> grep selinuxfs /proc/self/mountinfo | awk '{ print $5 }'
>>>>
>>>> $ grep selinuxfs /proc/self/mountinfo | awk '{ print $5 }'
>>>> /selinux /chroot/selinux
>>>>
>>>> -- This message was distributed to subscribers of the selinux
>>>> mailing list. If you no longer wish to subscribe, send mail to
>>>> majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux"
>>>> without quotes as the message.
>>>>
>>>>
>>>
>>> Second attempt.
>>
>> Technically I think we wanted to encapsulate all references to
>> selinuxfs by using libselinux, whether via direct bindings (as from
>> python) or by adding utils to libselinux (for shell scripts). For
>> example: $ gcc -lselinux -o getinitialcontext getinitialcontext.c $
>> ./getinitialcontext unlabeled system_u:object_r:unlabeled_t:s0
>>
> If we are going to add any more commands to libselinux I would prefer
> them to be prefixed with selinux or at lease se.
no problem, I can call it anything we want. Last issue I question is
better handling of there being no result. We wouldn't want to delete
context'**' :)
-Eric
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
