diff options
| author | Steve Grubb <sgrubb@redhat.com> | 2020-11-20 11:52:14 -0500 |
|---|---|---|
| committer | Daiki Ueno <dueno@src.gnome.org> | 2020-11-21 08:05:03 +0100 |
| commit | ebc7bc9efacc17049e54da8d96a4a29943621113 (patch) | |
| tree | 0d5b1df86e1cd758e9a688acc21075f8c7ca205d /po/nb.po | |
| parent | 4f531000ae49d89f800e00572271ad3d704a1a01 (diff) | |
| download | gnome-keyring-ebc7bc9efacc17049e54da8d96a4a29943621113.tar.gz | |
Update libcap-ng capability handling
There is a change in libcap-ng-0.8.1 that causes gnome-keyring to not
work correctly. The capng_apply function now returns an error if it
cannot change the bounding set. Previously this was ignored. Which means
now gnome-keyring exits when it shouldn't.
The new patch adds troubleshooting info to the error messages. And it checks
to see if we have CAP_SETPCAP. If we do not, then we cannot change the
bounding set and just set capabilities. On the setuid side, it now drops
the bounding set and clears any supplemental groups that may be left over
as an accident.
Diffstat (limited to 'po/nb.po')
0 files changed, 0 insertions, 0 deletions