Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I will be closing this bug as "WONTFIX".
The reason is that pam_cap module is not part of the standard PAM configuration for sshd,
the module tries to surpass security measures of openssh and linux kernel and overall is
not compatible with fundamental design of openssh. Therefore pam_cap module should not
be considered compatible with openssh.
To workaround this bug user can use su binary to su to himself to gain the capabilities
after using ssh. One option would be to create a custom shell binary that would run shell,
than self-su.
Here is a simple workaround demo using su:
1. # useradd testuser
2. # passwd testuser
3. # sed -i '1i auth optional pam_cap.so keepcaps defer' /etc/pam.d/su
4. # echo '^cap_chown *' > /etc/security/capability.conf
5. # ssh -l testuser localhost
6. # su testuser
7. $ grep Cap /proc/$$/status
CapInh: 0000000000000001
CapPrm: 0000000000000001
CapEff: 0000000000000001
CapBnd: 000001ffffffffff
CapAmb: 0000000000000001