From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: ls -Z on non-SE machine
Date: Sun, 15 May 2005 12:16:01 +0100 [thread overview]
Message-ID: <20050515111601.GF16326@lkcl.net> (raw)
In-Reply-To: <1116154619.7833.2.camel@localhost.localdomain>
On Sun, May 15, 2005 at 06:56:59AM -0400, Ivan Gyurdiev wrote:
> On Sun, 2005-05-15 at 11:27 +0100, Luke Kenneth Casson Leighton wrote:
> > how about just silently ignoring the -Z option if selinux is
> > detected to not be enabled?
>
> I believe that's what it does right now, and Russell's arguing against
> that behavior - he's saying you should be able to view the contexts,
> whether or not SELinux is running (unless I am misunderstanding).
no, it doesn't. an error is generated saying that the "-Z" argument is
not understood.
the resultant error (non-zero exit code) causes, for example,
initialisation scripts to fail.
the behaviour is also different: an error code is printed out on
stderr.
that's _not_ silent behaviour :)
yes, i am running my laptop with debian / selinux disabled, with
the se-aware coreutils package still installed on it.
every time i boot up, i get a "ls -Z" error in one of the key
initialisation scripts.
l.
--
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 prev parent reply other threads:[~2005-05-15 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 9:21 ls -Z on non-SE machine Russell Coker
2005-05-15 10:27 ` Luke Kenneth Casson Leighton
2005-05-15 10:56 ` Ivan Gyurdiev
2005-05-15 11:16 ` Luke Kenneth Casson Leighton [this message]
2005-05-15 11:11 ` Russell Coker
2005-05-15 16:37 ` Luke Kenneth Casson Leighton
2005-05-16 11:31 ` Stephen Smalley
2005-05-16 11:48 ` Russell Coker
2005-05-16 12:36 ` Stephen Smalley
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=20050515111601.GF16326@lkcl.net \
--to=lkcl@lkcl.net \
--cc=ivg2@cornell.edu \
--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.