Yes, this appears to be deliberate upstream behavior and I'm not sure we
should revert that. Marking incomplete, if there is further info please
share.
** Tags removed: foundations-triage-discuss
** Changed in: libcap2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/1700814
Title:
Default capability of cap_setfcap+i should be set on setcap
Status in libcap2 package in Ubuntu:
Incomplete
Bug description:
If I grant a user (via pam_cap) cap_setfcap+i, I would then expect
them to be able to use setcap without sudo. setcap is not provided
with any default file capabilities however, so either the user has to
sudo, or I have to grant the setfcap capability to setcap with setcap.
In my mind, it would be reasonable to grant setfcap+i to setcap by
default on installation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700814/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
