-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
This is not intended behavior. It should be fixed (aka such support
removed). Capabilities should only be available on executable files -
not directories, symlinks or anything else...
So do you plan on returning an error
--- Jan Engelhardt [EMAIL PROTECTED] wrote:
On Dec 26 2007 16:29, Andrew Morgan wrote:
I'm assuming it's unintended - or rather it's harmless but has no use -
but will let Andrew respond since he may have some cool idea i haven't
thought of.
This is not intended behavior. It
Quoting Andrew Morgan ([EMAIL PROTECTED]):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
Quoting Chris Friedhoff ([EMAIL PROTECTED]):
Hello,
in updating the documentation
http://www.friedhoff.org/posixfilecaps.html I discovered that it is
possible to
On Dec 26 2007 16:29, Andrew Morgan wrote:
I'm assuming it's unintended - or rather it's harmless but has no use -
but will let Andrew respond since he may have some cool idea i haven't
thought of.
This is not intended behavior. It should be fixed (aka such support
removed). Capabilities
Hello,
in updating the documentation
http://www.friedhoff.org/posixfilecaps.html I discovered that it is
possible to give directories through setcap also the extended attribute
capability and therefor grant them capabilities.
Is this is intended or maybe not ? If it's intended, what is the
Quoting Chris Friedhoff ([EMAIL PROTECTED]):
Hello,
in updating the documentation
http://www.friedhoff.org/posixfilecaps.html I discovered that it is
possible to give directories through setcap also the extended attribute
capability and therefor grant them capabilities.
Is this is intended
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
Quoting Chris Friedhoff ([EMAIL PROTECTED]):
Hello,
in updating the documentation
http://www.friedhoff.org/posixfilecaps.html I discovered that it is
possible to give directories through setcap also the extended
