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.
3. What is the nature and description of the request?
- The format that is used by "capsh --print" to print capabilities is misleading (when not having read trough "man cap_to_text") since it has a counter-intuitive interpretation.
Example:
# capsh --print |cat -n|head -3
1 Current: =ep
2 Bounding set = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read,cap_perfmon,cap_bpf,cap_checkpoint_restore
3 Ambient set =
Interpretation:
- The "Bounding set" stands out: It has lots of capabilities.
- Conclusion: when capabilities are here, there are clearly shown/printed
- The "Ambient Set" is empty, "The Current" is also empty and has a "ep" annotation. That annotation will do nothing as the set is empty anyway.
Reality:
- All Bits are set, that means FULL capabilities.
# cat /proc/$$/status|grep Cap |cat -n
1 CapInh: 0000000000000000
2 CapPrm: 000001ffffffffff
3 CapEff: 000001ffffffffff <- here
4 CapBnd: 000001ffffffffff
5 CapAmb: 0000000000000000
4. Why does the customer need this? (List the business requirements here)
- Prevent misinterpretation of capabilities when not aware of cap_to_text peculiarities.
- Security related features should be easy to understand and designed in a way which does not lead to misunderstanding.
5. How would the customer like to achieve this? (List the functional requirements here)
a) cap_to_text shall be changed to print "all=ep" instead "=ep" (same for "i"). That will resolve the misunderstanding.
b) The "Bounding set" and "Ambient set" should print ":" instead of "=", (the "=" comes from cap_to_text)
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Above example output should look like this:
# capsh --print
Current: all=ep -> "all" is printed
Bounding set: all -> "all" is printed rather than every singe capability
Ambient set: none -> "none" is printed rather than empty output
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
- no
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
- no, asap
9. Is the sales team involved in this request and do they have any additional input?
- no
10. List any affected packages or components.
- libcap-2.48-2.el8.x86_64
11. Would the customer be able to assist in testing this functionality if implemented?
- yes
Moving to RHEL 9 as we do not plan to do any other non-critical bugfixes in RHEL8.
Comment 4RHEL Program Management
2023-08-30 15:15:25 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-08-30 15:16:58 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.
Users watching this BZ may not be automatically added to the Jira ticket. Be sure to add yourself to the Watchers field in the Jira issue if you desire to continue following this issue.
3. What is the nature and description of the request? - The format that is used by "capsh --print" to print capabilities is misleading (when not having read trough "man cap_to_text") since it has a counter-intuitive interpretation. Example: # capsh --print |cat -n|head -3 1 Current: =ep 2 Bounding set = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_module,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_mac_override,cap_mac_admin,cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read,cap_perfmon,cap_bpf,cap_checkpoint_restore 3 Ambient set = Interpretation: - The "Bounding set" stands out: It has lots of capabilities. - Conclusion: when capabilities are here, there are clearly shown/printed - The "Ambient Set" is empty, "The Current" is also empty and has a "ep" annotation. That annotation will do nothing as the set is empty anyway. Reality: - All Bits are set, that means FULL capabilities. # cat /proc/$$/status|grep Cap |cat -n 1 CapInh: 0000000000000000 2 CapPrm: 000001ffffffffff 3 CapEff: 000001ffffffffff <- here 4 CapBnd: 000001ffffffffff 5 CapAmb: 0000000000000000 4. Why does the customer need this? (List the business requirements here) - Prevent misinterpretation of capabilities when not aware of cap_to_text peculiarities. - Security related features should be easy to understand and designed in a way which does not lead to misunderstanding. 5. How would the customer like to achieve this? (List the functional requirements here) a) cap_to_text shall be changed to print "all=ep" instead "=ep" (same for "i"). That will resolve the misunderstanding. b) The "Bounding set" and "Ambient set" should print ":" instead of "=", (the "=" comes from cap_to_text) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Above example output should look like this: # capsh --print Current: all=ep -> "all" is printed Bounding set: all -> "all" is printed rather than every singe capability Ambient set: none -> "none" is printed rather than empty output 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? - no 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)? - no, asap 9. Is the sales team involved in this request and do they have any additional input? - no 10. List any affected packages or components. - libcap-2.48-2.el8.x86_64 11. Would the customer be able to assist in testing this functionality if implemented? - yes