Pádraig Brady wrote:
> Updated patch attached.
One more, please ;-)
> +...@item --preserve-context
> +...@opindex --preserve-context
> +...@cindex SElinux
> +...@cindex security context
> +Preserve the SELinux security context of files and directories.
> +Failure to preserve the context in all of
Andreas Schwab wrote:
> Pádraig Brady writes:
>
>> @@ -8045,6 +8055,15 @@ ownership of installed files or directories to
>> @var{owner}. The default
>> is @code{root}. @var{owner} may be either a user name or a numeric user
>> ID.
>>
>> +...@itemx --preserve-context
>
> s/@itemx/@item/
Pádraig Brady wrote:
> Jim Meyering wrote:
>> Pádraig Brady wrote:
>>> Pádraig Brady wrote:
Jim Meyering wrote:
> You might want to do something similar to what I did in fts.c
> with this change:
>
> http://git.sv.gnu.org/cgit/gnulib.git/commit/?id=97d5b66578be507
Oh
Pádraig Brady wrote:
> Pádraig Brady wrote:
>> Jim Meyering wrote:
>>> You might want to do something similar to what I did in fts.c
>>> with this change:
>>>
>>> http://git.sv.gnu.org/cgit/gnulib.git/commit/?id=97d5b66578be507
>>
>> Oh cool, thanks for that.
>
> Hmm, looks like my Fedora 8 sys
Jim Meyering wrote:
> Pádraig Brady wrote:
>> Pádraig Brady wrote:
>>> Jim Meyering wrote:
You might want to do something similar to what I did in fts.c
with this change:
http://git.sv.gnu.org/cgit/gnulib.git/commit/?id=97d5b66578be507
>>> Oh cool, thanks for that.
>> Hmm, l
Pádraig Brady wrote:
> Jim Meyering wrote:
>> Pádraig Brady wrote:
>> ...
>>> I'll also look at documenting the ls SElinux options in the info docs
>>> as I couldn't see them on a quick search.
>>
>> Nice. That will we welcome.
>> If you feel really industrious, mktemp needs info documentation, to
Pádraig Brady writes:
> @@ -8045,6 +8055,15 @@ ownership of installed files or directories to
> @var{owner}. The default
> is @code{root}. @var{owner} may be either a user name or a numeric user
> ID.
>
> +...@itemx --preserve-context
s/@itemx/@item/
Andreas.
--
Andreas Schwab, sch...@
Pádraig Brady wrote:
> Jim Meyering wrote:
>> You might want to do something similar to what I did in fts.c
>> with this change:
>>
>> http://git.sv.gnu.org/cgit/gnulib.git/commit/?id=97d5b66578be507
>
> Oh cool, thanks for that.
Hmm, looks like my Fedora 8 system at least with SELinux disabl
Jim Meyering wrote:
> Pádraig Brady wrote:
> ...
>> I'll also look at documenting the ls SElinux options in the info docs
>> as I couldn't see them on a quick search.
>
> Nice. That will we welcome.
> If you feel really industrious, mktemp needs info documentation, too.
Ah the SELinux stuff was
Pádraig Brady wrote:
...
> I'll also look at documenting the ls SElinux options in the info docs
> as I couldn't see them on a quick search.
Nice. That will we welcome.
If you feel really industrious, mktemp needs info documentation, too.
___
Bug-core
Jim Meyering wrote:
> You might want to do something similar to what I did in fts.c
> with this change:
>
> http://git.sv.gnu.org/cgit/gnulib.git/commit/?id=97d5b66578be507
Oh cool, thanks for that.
I'll also look at documenting the ls SElinux options in the info docs
as I couldn't see them o
Pádraig Brady wrote:
> Just a quick follow up to this now archived bug:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472590
>
> The last message there mentioned selinux query overhead.
> On my system with selinux disabled, there is currently
> a significant overhead in doing the selinux looku
Just a quick follow up to this now archived bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472590
The last message there mentioned selinux query overhead.
On my system with selinux disabled, there is currently
a significant overhead in doing the selinux lookup per file
with a standard `ls -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering wrote:
> Russell Coker <[EMAIL PROTECTED]> wrote:
>
>> On Saturday 25 October 2008 00:19, Mike Edenfield <[EMAIL PROTECTED]> wrote:
>>> Jim Meyering wrote:
A desire for compatibility makes "+" look good.
"." is appealing for SEL
Russell Coker <[EMAIL PROTECTED]> wrote:
> On Saturday 25 October 2008 00:19, Mike Edenfield <[EMAIL PROTECTED]> 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 SELi
On Saturday 25 October 2008 00:19, Mike Edenfield <[EMAIL PROTECTED]> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mike Edenfield on 10/24/2008 7:19 AM:
> 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:
>
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
Vikram Noel Ambrose <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> wrote:
...
if (SELinux, with no other MAC or ACL)
use '.'
else if (any other combination of alternate access methods)
use '+'
...
>>> Here's sample output, running on an SELinux
Jim Meyering <[EMAIL PROTECTED]> wrote:
[ I'm Cc'ing [EMAIL PROTECTED]
FYI, this is a continuation of discussion from the SELinux list:
http://marc.info/?t=12064507403&r=1&w=2
and the debian bug tracking system: http://bugs.debian.org/472590
The problem is that on an SELinux-enabled
Jim Meyering <[EMAIL PROTECTED]> wrote:
> I wrote this:
>> [ I'm Cc'ing [EMAIL PROTECTED]
>> FYI, this is a continuation of discussion from the SELinux list:
>> http://marc.info/?t=12064507403&r=1&w=2
>> and the debian bug tracking system: http://bugs.debian.org/472590
>>
>> The problem
21 matches
Mail list logo
