From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] libcap-ng: Update to 0.8.2
Date: Mon, 26 Apr 2021 14:31:18 +0200 [thread overview]
Message-ID: <20210426123118.3783294-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4258 bytes --]
- Update from 0.7.9 to 0.8.2
- Update rootfile
- Changelog
0.8.2
- In capng_apply, if we blew up in bounding set, allow setting capabilities
- If PR_CAP_AMBIENT is not available, do not build libdrop_ambient
- Improve last_cap check
0.8.1
- If procfs is not available, leave last_cap as CAP_LAST_CAP
- If bounding and ambient not found in status, try prctl method
- In capng_apply, move ambient caps to the end of the transaction
- In capng_apply, return errors more aggressively.
- In capng_apply, if the action includes the bounding set,resync with the kernel
- Fix signed/unsigned warning in cap-ng.c
- In capng_apply, return a unique error code to diagnose any failure
- In capng_have_capability, return 0 for failure
- Add the libdrop_ambient admin tool
0.8
- Add vararg support to python bindings for capng_updatev
- Add support for ambient capabilities
- Add support for V3 filesystem capabilities
0.7.11
- Really clear bounding set if asked in capng_change_id
- Add CAP_PERFMON, CAP_BPF, & CAP_CHECKPOINT_RESTORE
- Avoid malloc/free in capng_apply (Natanael Copa)
- If procfs is not available, get bounding set via prctl
- Cleanup some compiler warnings
0.7.10
- Update capng_change_id man page
- Add capng_have_permitted_capabilities function
- Update filecap to output which set the capabilities are in
- Fix filecap to not output an error when a file has no capabilities
- Add udplite support to netcap
- Fix usage of pthread_atfork (Joe Orton)
- Mark processes in child user namespaces with * (Danila Kiver)
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
config/rootfiles/common/libcap-ng | 17 ++++++++---------
lfs/libcap-ng | 4 ++--
2 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/config/rootfiles/common/libcap-ng b/config/rootfiles/common/libcap-ng
index 5a02dd7d6..2571cd26a 100644
--- a/config/rootfiles/common/libcap-ng
+++ b/config/rootfiles/common/libcap-ng
@@ -7,23 +7,21 @@
#usr/lib/libcap-ng.so
usr/lib/libcap-ng.so.0
usr/lib/libcap-ng.so.0.0.0
+#usr/lib/libdrop_ambient.la
+#usr/lib/libdrop_ambient.so
+usr/lib/libdrop_ambient.so.0
+usr/lib/libdrop_ambient.so.0.0.0
#usr/lib/pkgconfig/libcap-ng.pc
-#usr/lib/python2.7/site-packages/_capng.la
-#usr/lib/python2.7/site-packages/_capng.so
-#usr/lib/python2.7/site-packages/capng.py
-#usr/lib/python2.7/site-packages/capng.pyc
-#usr/lib/python2.7/site-packages/capng.pyo
-#usr/lib/python3.8/site-packages/_capng.la
-#usr/lib/python3.8/site-packages/_capng.so
-#usr/lib/python3.8/site-packages/capng.py
#usr/share/aclocal/cap-ng.m4
#usr/share/man/man3/capng_apply.3
+#usr/share/man/man3/capng_apply_caps_fd.3
#usr/share/man/man3/capng_capability_to_name.3
#usr/share/man/man3/capng_change_id.3
#usr/share/man/man3/capng_clear.3
#usr/share/man/man3/capng_fill.3
#usr/share/man/man3/capng_get_caps_fd.3
#usr/share/man/man3/capng_get_caps_process.3
+#usr/share/man/man3/capng_get_rootid.3
#usr/share/man/man3/capng_have_capabilities.3
#usr/share/man/man3/capng_have_capability.3
#usr/share/man/man3/capng_lock.3
@@ -32,10 +30,11 @@ usr/lib/libcap-ng.so.0.0.0
#usr/share/man/man3/capng_print_caps_text.3
#usr/share/man/man3/capng_restore_state.3
#usr/share/man/man3/capng_save_state.3
-#usr/share/man/man3/capng_set_caps_fd.3
+#usr/share/man/man3/capng_set_rootid.3
#usr/share/man/man3/capng_setpid.3
#usr/share/man/man3/capng_update.3
#usr/share/man/man3/capng_updatev.3
+#usr/share/man/man7/libdrop_ambient.7
#usr/share/man/man8/captest.8
#usr/share/man/man8/filecap.8
#usr/share/man/man8/netcap.8
diff --git a/lfs/libcap-ng b/lfs/libcap-ng
index 0cbe3e634..ef9c3e1f2 100644
--- a/lfs/libcap-ng
+++ b/lfs/libcap-ng
@@ -24,7 +24,7 @@
include Config
-VER = 0.7.9
+VER = 0.8.2
THISAPP = libcap-ng-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 2398d695508fab9ce33668c53a89b0e9
+$(DL_FILE)_MD5 = faf1ef766cf068ad1aba4008ced665f7
install : $(TARGET)
--
2.31.1
reply other threads:[~2021-04-26 12:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210426123118.3783294-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox