[Bug 1700814] Re: Default capability of cap_setfcap+i should be set on setcap

2022-05-25 Thread Balint Reczey
@serge-hallyn I'm not sure why I got this bug assigned. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700814 Title: Default capability of cap_setfcap+i should be set on setcap To manage

[Bug 1700814] Re: Default capability of cap_setfcap+i should be set on setcap

2022-05-20 Thread Serge Hallyn
** Changed in: libcap2 (Ubuntu) Assignee: Serge Hallyn (serge-hallyn) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700814 Title: Default capability of

[Bug 1700814] Re: Default capability of cap_setfcap+i should be set on setcap

2018-02-26 Thread Serge Hallyn
Even unprivileged containers are now usable in containers with the right kernel, so this would be a good thing to add to the packaging. I'm not sure when I'll have time, but assigning to myself so that I can more easily find it when I do. ** Changed in: libcap2 (Ubuntu) Assignee:

[Bug 1700814] Re: Default capability of cap_setfcap+i should be set on setcap

2017-06-29 Thread Serge Hallyn
Indeed it should be reasonable to do so. Note that there are cases, including unprivileged containers, where file capabilities cannot be set, so the packaging would have to gracefully handle (i.e. ignore) that failure rather than fail the package install. -- You received this bug notification