RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2037215 - Ambient capabilities failed to applied to non-root user even when correct rules are in /etc/security/capability.conf
Summary: Ambient capabilities failed to applied to non-root user even when correct rul...
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-01-25
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libcap
Version: 9.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Zoltan Fridrich
QA Contact: Martin Zelený
Jan Fiala
URL:
Whiteboard:
Depends On: 2037212
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-05 09:19 UTC by Zoltan Fridrich
Modified: 2022-05-17 16:37 UTC (History)
12 users (show)

Fixed In Version: libcap-2.48-8.el9
Doc Type: Bug Fix
Doc Text:
.Ambient capabilities are now applied correctly to non-root users As a safety measure, changing a UID (User Identifier) from root to non-root nullifies permitted, effective, and ambient sets of capabilities. However, the `pam_cap.so` module is unable to set ambient capabilities because a capability needs to be in both the permitted and the inheritable set to be in the ambient set. In addition, the permitted set gets nullified after changing the UID (for example by using the `setuid` utility), so the ambient capability cannot be set. To fix this problem, the `pam_cap.so` module now supports the `keepcaps` option, which allows a process to retain its permitted capabilities after changing the UID from root to non-root. The `pam_cap.so` module now also supports the `defer` option, which causes `pam_cap.so` to reapply ambient capabilities within a callback to `pam_end()`. This callback can be used by other applications after changing the UID. Therefore, if the `su` and `login` utilities are updated and PAM-compliant, you can now use `pam_cap.so` with the `keepcaps` and `defer` options to set ambient capabilities for non-root users.
Clone Of: 1950187
Environment:
Last Closed: 2022-05-17 16:02:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-106854 0 None None None 2022-01-05 09:21:39 UTC
Red Hat Issue Tracker SECENGSP-4241 0 None None None 2022-01-05 09:21:50 UTC
Red Hat Product Errata RHBA-2022:4040 0 None None None 2022-05-17 16:02:26 UTC

Comment 15 errata-xmlrpc 2022-05-17 16:02:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: libcap), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4040
Note You need to log in before you can comment on or make changes to this bug.