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.

Description of problem:
Files in documentation folder have 'loose' permissions:
    In the file /usr/share/doc/slf4j-1.7.4/APACHE-LICENSE , the permission is 0664. 0755 is expected or more restrictive

Version-Release number of selected component (if applicable):
    slf4j-1.7.4-4.el7_4.noarch

Additional info:
Customer has security checker that complains about loose permissions for tomcat documentation files. Customer is concerned that group-write permissions to the documentation files may affect the security of the system and requesting for removing write permissions on group.

Thanks for the report.  Although the permissions could be changed, we are not currently planning to update this component.  Since the file's group is also root there is no obvious security issue here and 0664/root.root 0644/root.root are functionally equivalent.

We'll correct this upstream for future releases.