Debian Patches
Status for libcap2/1:2.73-4
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Hide-private-symbols.patch | Hide private symbols Hide a symbol which is clearly meant to be private. This resolves a FTBFS in combination with the new build dependency gperf. |
Christian Kastner <ckk@debian.org> | no | debian | 2022-03-04 | |
| Filter-out-PIE-flags-when-building-shared-objects.patch | Filter out PIE flags when building shared objects Filter out -pie, -fpie, and -fPIE when building the shared library and the PAM module. This way, hardening=+all can be used unconditionally in debian/rules. |
Christian Kastner <ckk@kvr.at> | not-needed | 2022-03-04 | ||
| Skip-git-if-not-installed.patch | Skip git if not installed This is only used during the clean stage. For a typical Debian package build, git will not be installed. |
Christian Kastner <ckk@debian.org> | no | debian | 2024-02-06 | |
| pam_cap-Fix-potential-configuration-parsing-error.patch | pam_cap: Fix potential configuration parsing error The current configuration parsing does not actually skip user names that do not start with @, but instead treats the name as a group name for further parsing, which can result in matching unexpected capability sets and may trigger potential security issues. Only names starting with @ should be parsed as group names. |
Tianjia Zhang <tianjia.zhang@linux.alibaba.com> | no | 2025-02-17 | ||
| Add-a-test-for-bad-group-prefix.patch | Add a test for bad group prefix. The previous commit fixed a bug with the config parsing in pam_cap. This is a test that we don't regress against that fix. |
"Andrew G. Morgan" <morgan@kernel.org> | no | 2025-02-16 |
All known versions for source package 'libcap2'
- 1:2.73-4 (sid)
- 1:2.66-5 (trixie)
- 1:2.66-4 (bookworm, bookworm-backports)
- 1:2.44-1 (bullseye, bullseye-security)