On Thu, 13 Nov 2008, Andrew G. Morgan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew G. Morgan wrote:
So assuming I can't rely on cap_compare() always being there (it being
Linux-specific extension and even then only in very recent libcap),
would the following be a reasonable
Panu and all,
thanks for implementing this feature!
Andreas
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Panu,
The following change looks a little problematic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Panu Matilainen wrote:
On Thu, 30 Oct 2008, Andrew G. Morgan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Panu,
The following change looks a little problematic:
On Thu, 30 Oct 2008, Andrew G. Morgan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Panu,
The following change looks a little problematic:
On Sat, 25 Oct 2008, Andrew G. Morgan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Panu Matilainen wrote:
I'm ok with adding the functionality they provide, but I think we should
use libcap and libacl instead of looking at the extended attributes
directly. libacl and libcap provide
On Mon, 1 Sep 2008, Andreas Gruenbacher wrote:
Hello all,
I am trying to get the minimal bits and pieces into place for allowing us to
start using file capabilties.
Cool.
Currently, rpm neither supports acls nor file capabilities [1], and so when
they are needed, the usual way is to set
