From: Daniel J Walsh <dwalsh@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: russell@coker.com.au, "Mike Edenfield" <kutulu@kutulu.org>,
472590@bugs.debian.org, bug-coreutils@gnu.org,
"Vikram Noel Ambrose" <noel.ambrose@gmail.com>,
selinux@tycho.nsa.gov, "Ondr(ej Vas(ík" <ovasik@redhat.com>
Subject: Re: RFC: changing the "+" in ls -l output to be "." or "+"
Date: Fri, 31 Oct 2008 09:37:53 -0400 [thread overview]
Message-ID: <490B0A31.8090907@redhat.com> (raw)
In-Reply-To: <87y70bu6ah.fsf@rho.meyering.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Meyering wrote:
> Russell Coker <russell@coker.com.au> wrote:
>
>> On Saturday 25 October 2008 00:19, Mike Edenfield <kutulu@kutulu.org> wrote:
>>> Jim Meyering wrote:
>>>> A desire for compatibility makes "+" look good.
>>>> "." is appealing for SELinux-only because it's inconspicuous.
>>> Speaking as a fairly new SELinux user/admin, having a "."
>>> next to every file in my ls output is just as useful or
>>> non-useful as having a "+" next to them, so does it really
>>> buy anything? I end up needing -Z either way.
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472590
>>
>> The above URL has the history of this discussion. I requested that there be
>> no such notification. I still believe that there should be nothing used in
>> the case of SE Linux (although I could be convinced that the "." is OK if
>> files with the context "system_u:object_r:file_t:s0" did not have it).
>>
>> But it seems that I have lost this debate. Using "." is better than "+", and
>> my request to have none of this in Lenny has been accepted so we have some
>> time to work on this before Lenny+1.
>>
>>> Based on the kind of real-world problems I've had, the most
>>> useful thing ls could tell me about a file on my SELinux
>>> system would be that it *should* have a label and *doesn't*,
>>> something like:
>>>
>>> if ( selinux_enabled )
>>> if ( label == NULL || label == fs.defaultlabel )
>>> use "!"
>>> else
>>> use " "
>>> else if ( anything else )
>>> use "+"
>> That sounds quite reasonable.
>
> Actually, I'm leaning your way, now, and agree.
>
> If you, Russell, write the patch (w/NEWS and docs would be really nice)
> I'll make the switch upstream pretty soon. It'd be nice to give the
> austin group a heads up, too, since this behavior would be contrary to
> POSIX. I don't think it's worth it to make this depend on the setting
> of the POSIXLY_CORRECT envvar.
>
> --
> 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.
If you really wanted to go wild, you could add a qualifier to check
matchpathcon to indicate it differs from the default for the file
system, although it would be very expensive. Perhaps find would be a
better source. "find" all files not matching the system defaults.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkkLCjEACgkQrlYvE4MpobM3ywCfZtVW9cQE8hgLRVCHYqHKLfU1
cWgAn2/cx41bmoFguBEVJXGbUiqsryzH
=+qTw
-----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:[~2008-10-31 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 4:23 ls in Debian/Unstable Russell Coker
2008-03-25 14:09 ` Casey Schaufler
2008-03-25 15:08 ` Jim Meyering
2008-03-25 21:22 ` Russell Coker
[not found] ` <20080325173116.GQ2626@mathom.us>
2008-03-25 21:24 ` Bug#472590: " Russell Coker
2008-03-25 21:28 ` Jim Meyering
[not found] ` <20080325234310.GR2626@mathom.us>
2008-03-26 5:12 ` Russell Coker
2008-03-31 9:02 ` Jim Meyering
2008-03-31 9:23 ` Russell Coker
2008-03-31 9:43 ` Jim Meyering
2008-04-02 20:33 ` RFC: changing the "+" in ls -l output to be "." or "+" Jim Meyering
2008-10-23 12:20 ` Jim Meyering
2008-10-24 3:18 ` Vikram Noel Ambrose
2008-10-24 7:04 ` Jim Meyering
2008-10-24 13:19 ` Mike Edenfield
2008-10-26 7:46 ` Russell Coker
2008-10-26 8:09 ` Jim Meyering
2008-10-31 13:37 ` 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=490B0A31.8090907@redhat.com \
--to=dwalsh@redhat.com \
--cc=472590@bugs.debian.org \
--cc=bug-coreutils@gnu.org \
--cc=jim@meyering.net \
--cc=kutulu@kutulu.org \
--cc=noel.ambrose@gmail.com \
--cc=ovasik@redhat.com \
--cc=russell@coker.com.au \
--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.