From: Russell Coker <russell@coker.com.au>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: ls -Z on non-SE machine
Date: Sun, 15 May 2005 21:11:31 +1000 [thread overview]
Message-ID: <200505152111.34732.russell@coker.com.au> (raw)
In-Reply-To: <20050515102704.GA16326@lkcl.net>
On Sunday 15 May 2005 20:27, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> how about just silently ignoring the -Z option if selinux is
> detected to not be enabled?
>
> or placing dummy information in its place which any selinux-aware
> shell scripts can pick up on.
You appear to have totally ignored my points about analysis of SE Linux disks
in non-SE machines and recovery of SE Linux systems from non-SE rescue disks.
We could just not use the -Z option if we don't want the security contexts to
be displayed. But the entire point here is to have them available.
> On Sun, May 15, 2005 at 07:21:20PM +1000, Russell Coker wrote:
> > Currently "ls -Z" refuses to operate if it detects that SE Linux is not
> > enabled on the machine.
> >
> > This makes no sense to me. Files that are labelled when running SE Linux
> > keep their labels (and the values of such labels may still be read) when
> > not running SE Linux. It seems quite reasonable to me that an
> > administrator may want to take a disk out of a SE Linux machine and mount
> > it on a non-SE machine for debugging problems or forensics. The current
> > behavior of ls works against such operations.
> >
> > I believe that the best thing to do is to have ls not be linked against
> > libselinux and instead just call the XATTR api for reading the file
> > contexts. Ideally I think that such functionality should be enabled
> > unconditionally so that any administrator who receives a disk that was
> > used on a SE Linux system will have the ability to conveniently view all
> > the data on it.
> >
> > --
> > http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux
> > packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> > http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> > http://www.coker.com.au/~russell/ My home page
> >
> > --
> > 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.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
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:14 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
2005-05-15 11:11 ` Russell Coker [this message]
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=200505152111.34732.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=lkcl@lkcl.net \
--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.