From: Daniel J Walsh <dwalsh@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
selinux@tycho.nsa.gov
Subject: Re: [PATCH 029/155] policycoreutils: fixfiles clean up /var/run and
Date: Fri, 05 Aug 2011 11:34:22 -0400 [thread overview]
Message-ID: <4E3C0D7E.3070306@redhat.com> (raw)
In-Reply-To: <4E3C07E6.4030406@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/05/2011 11:10 AM, Eric Paris wrote:
> 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@tycho.nsa.gov 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'**' :)
>
Well it would actually delete *:*, and they are tmp files ...
echo "" | secon -t
secon: Couldn't read security context: Invalid argument
[Exit 1]
touch /tmp/dan1
# touch /tmp/empty
# cat /tmp/empty | secon -t
secon: Couldn't read security context: Invalid argument
[Exit 1]
So I think you are going to get an error and the app will blow up.
> -Eric
>
>
> -- 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.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk48DX4ACgkQrlYvE4MpobONaQCfTFsE84KQ4kiM1Y13+sz2ydyu
ZvcAoMihWiC9u+v0J/0gBrhc9iSkPbm5
=7VRP
-----END PGP SIGNATURE-----
--
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.
prev parent reply other threads:[~2011-08-05 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 20:56 [PATCH 029/155] policycoreutils: fixfiles clean up /var/run and Daniel J Walsh
2011-08-04 14:56 ` Stephen Smalley
2011-08-04 16:42 ` Daniel J Walsh
2011-08-04 17:33 ` Eric Paris
2011-08-04 19:16 ` Christopher J. PeBenito
[not found] ` <CACLa4puk2gO=aV=oNj-Kmj=eSmYmquX0skKoCxso6o9tWcf_Ng@mail.gmail.com>
2011-08-04 19:33 ` Stephen Smalley
2011-08-04 20:26 ` Daniel J Walsh
2011-08-04 21:00 ` Eric Paris
2011-08-04 21:06 ` Daniel J Walsh
2011-08-04 21:10 ` Eric Paris
2011-08-04 21:50 ` Daniel J Walsh
2011-08-05 14:18 ` Stephen Smalley
2011-08-05 14:45 ` Daniel J Walsh
2011-08-05 15:10 ` Eric Paris
2011-08-05 15:34 ` Daniel J Walsh [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=4E3C0D7E.3070306@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.