Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1702434 - foreman-bootloaders-redhat-tftpboot expected file permissions in package don't match runtime permissions
Summary: foreman-bootloaders-redhat-tftpboot expected file permissions in package don'...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.4.2
Hardware: All
OS: All
unspecified
medium
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-23 18:54 UTC by Ryan Mullett
Modified: 2023-12-15 16:27 UTC (History)
5 users (show)

Fixed In Version: foreman-bootloaders-redhat-202004171200-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:58:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Dist git change (3.29 KB, patch)
2019-04-24 09:28 UTC, Lukas Zapletal 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:58:50 UTC

Description Ryan Mullett 2019-04-23 18:54:41 UTC 
Description of problem:
File permissions from the rpm do not match the runtime permissions on several files. This results in mode failures on rpm -Va. Most noticed on systems in which DISA STIG is being performed and file permissions should not be less than the rpm provides or it is considered a finding during an audit. Important for government users and contractors who will be performing DISA STIG. 

Version-Release number of selected component (if applicable):
foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install and configure Satellite server
2. rpm -V foreman-bootloaders-redhat-tftpboot

Actual results:
The following files have permissions that are more permissive than the rpm provides:

/var/lib/tftpboot/grub2
/var/lib/tftpboot/grub2/grubia32.0
/var/lib/tftpboot/grub2/grubia32.efi
/var/lib/tftpboot/grub2/grubx64.efi
/var/lib/tftpboot/grub2/shim.efi
/var/lib/tftpboot/grub2/shimx64.efi
/var/lib/tftpboot/grub2/shimx64-redhat.efi

Expected results:
The file permissions provided via rpm should match the final runtime permissions (or they should be less restrictive on the rpm than the runtime permissions, which would not result in a finding).

Additional info:
The following output shows what it "should be" according to the rpm, as well as what it "actually is" after the package has been installed. This could be resolved by using the proper permissions in the spec file, so that rpm -Va will not flag on these files.

From rpm: foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
/var/lib/tftpboot/grub2
SHOULD BE:  000
ACTUALLY IS:  755
--
From rpm: foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
/var/lib/tftpboot/grub2/grubia32.0
SHOULD BE:  000
ACTUALLY IS:  644
--
From rpm: foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
/var/lib/tftpboot/grub2/grubia32.efi
SHOULD BE:  000
ACTUALLY IS:  644
--
From rpm: foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
/var/lib/tftpboot/grub2/grubx64.efi
SHOULD BE:  000
ACTUALLY IS:  644
--
From rpm: foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
/var/lib/tftpboot/grub2/shim.efi
SHOULD BE:  000
ACTUALLY IS:  644
--
From rpm: foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
/var/lib/tftpboot/grub2/shimx64.efi
SHOULD BE:  000
ACTUALLY IS:  644
--
From rpm: foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch
/var/lib/tftpboot/grub2/shimx64-redhat.efi
SHOULD BE:  000
ACTUALLY IS:  644
Comment 4 Lukas Zapletal 2019-04-24 09:28:58 UTC 
Created attachment 1558045 [details]
Dist git change
Comment 9 Lukas Zapletal 2020-05-27 06:45:02 UTC 
For the record, I made a patch upstream to sync the change. I forgot that we have upstreamed this some time ago. I, I upstreamed this :-)
Comment 10 Lukas Pramuk 2020-10-06 22:43:11 UTC 
VERIFIED.

@Satellite 6.8.0 Snap18
foreman-bootloaders-redhat-tftpboot-202005201200-1.el7sat.noarch

by the following manual reproducer:

# rpm -V foreman-bootloaders-redhat-tftpboot
.....U...  g /var/lib/tftpboot/grub2/shimx64.efi

>>> there are no M (= The file's mode has changed) flags for the files from rpm
Comment 13 errata-xmlrpc 2020-10-27 12:58:35 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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366
Note You need to log in before you can comment on or make changes to this bug.