From: Daniel J Walsh <dwalsh@redhat.com>
To: Jim Meyering <meyering@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: re: id -Z subsumed by secon?
Date: Tue, 08 Aug 2006 14:58:29 -0400 [thread overview]
Message-ID: <44D8DED5.4040304@redhat.com> (raw)
>
>
> James Antill <james.antill@redhat.com> wrote:
>
>> > No, what Steven was saying is that the label for execcon will be reset
>> > on exec (after doing it's thing). To see this visually use "secon
>> > --self-exec" instead of id.
>> >
>> > % secon
>> > user: user_u
>>
> ...
>
> Thanks for the example.
>
> By the way, doesn't secon make id's -Z option unnecessary?
> I'm planning not to include the 'id -Z' patches upstream,
> Instead, runcon (with neither CONTEXT nor COMMAND) will
> print the current security context -- to be analogous to how nice(1)
> works if you don't give it a command.
>
> Any objection?
>
>
>
Yes I would like to maintain the idea of "-Z" being the way to view
contexts. This makes it easy for
a user to figure out how to see what context is being used. ls -Z, ps
-Z, netstat -Z ...
--
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.
next reply other threads:[~2006-08-08 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 18:58 Daniel J Walsh [this message]
2006-08-09 13:19 ` id -Z subsumed by secon? Janak Desai
2006-08-09 14:03 ` stat's -Z/--context option is gone [Re: " Jim Meyering
2006-08-09 13:55 ` Karl MacMillan
2006-08-09 14:05 ` Jim Meyering
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 13:16 setexeccon vs. setfscreatecon Jim Meyering
2006-08-08 15:21 ` Stephen Smalley
2006-08-08 15:57 ` Jim Meyering
2006-08-08 16:20 ` James Antill
[not found] ` <878xlzcflx.fsf_-_@rho.meyering.net>
2006-08-08 17:32 ` id -Z subsumed by secon? James Antill
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=44D8DED5.4040304@redhat.com \
--to=dwalsh@redhat.com \
--cc=meyering@redhat.com \
--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.