libcap-ng 0.8.1 tightened the error checking on capng_apply [1], returning an error of -4 [2] when trying to update the capability bounding set without having the CAP_SETPCAP capability to be able to do so. Existing applications need to accommodate these changes [3], see e.g. the corresponding changes in GNOME Keyring [4]. This patch series fixes mount.cifs and cifs.upall to work with libcapn-ng 0.8.1, while maintaining backwards compatibility with previous versions. [1] https://github.com/stevegrubb/libcap-ng/commit/6a24a9c5e2f3af1d56430417ee8c9a04ead38e6c [2] https://github.com/stevegrubb/libcap-ng/commit/2ab6a03b78cfa7620641c772d13ddbf3b405576b [3] https://github.com/stevegrubb/libcap-ng/issues/21 [4] https://gitlab.gnome.org/GNOME/gnome-keyring/-/commit/ebc7bc9efacc17049e54da8d96a4a29943621113 Jonas Witschel (2): mount.cifs: update the cap bounding set only when CAP_SETPCAP is given cifs.upall: update the cap bounding set only when CAP_SETPCAP is given cifs.upcall.c | 7 ++++++- mount.cifs.c | 7 ++++++- 2 files changed, 12 insertions(+), 2 deletions(-) -- 2.29.2
