From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Russell Coker <russell@coker.com.au>,
James Morris <jmorris@redhat.com>,
SE Linux <selinux@tycho.nsa.gov>
Subject: Re: ls --context of /selinux
Date: Tue, 02 Sep 2003 10:45:18 -0400 [thread overview]
Message-ID: <3F54ACFE.8090807@redhat.com> (raw)
In-Reply-To: <1062506326.18568.27.camel@moss-spartans.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
I have recieved a bug report on this, so I am fixing and should have a
new rpm today.
Dan
Stephen Smalley wrote:
>On Tue, 2003-09-02 at 03:23, Russell Coker wrote:
>
>
>>What are the plans regarding "ls --context /selinux"?
>>
>>Currently the lgetxattr() system call returns -1 (EOPNOTSUPP) and the current
>>ls patch (taken from Dan's repository) refuses to even allow "ls -l" because
>>of it (probably a bug in ls as I imagine that there will always be file
>>systems that don't support it).
>>
>>Will "ls --context /selinux" ever work?
>>
>>
>
>Since SELinux migrated to using xattr, the utilities can only get and
>set the contexts of files in a filesystem if it provides an xattr
>handler. There doesn't seem to be any reason to support getting or
>setting contexts on selinuxfs entries, so I wouldn't expect us to
>implement an xattr handler for it. The 'ls' in the patched coreutils
>from the NSA SELinux site simply displays (null) in the context field
>for such filesystems; I'm not sure why Dan has changed the behavior in
>his latest patch. There will always be at least some filesystem types
>that will not provide xattr handlers, so it does need to cleanly handle
>this case.
>
>
>
[-- Attachment #2: Type: text/html, Size: 1538 bytes --]
prev parent reply other threads:[~2003-09-02 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 7:23 ls --context of /selinux Russell Coker
2003-09-02 12:38 ` Stephen Smalley
2003-09-02 14:45 ` 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=3F54ACFE.8090807@redhat.com \
--to=dwalsh@redhat.com \
--cc=jmorris@redhat.com \
--cc=russell@coker.com.au \
--cc=sds@epoch.ncsc.mil \
--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.