Bug 1379290 - shipped policy file checksum differs from checksum of shipped policy file
Summary: shipped policy file checksum differs from checksum of shipped policy file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Dalibor Pospíšil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-26 09:37 UTC by Dalibor Pospíšil
Modified: 2019-03-12 09:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-12 09:12:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dalibor Pospíšil 2016-09-26 09:37:12 UTC
Description of problem:
policy.30 file check sum is different that the one shipped in .policy.sha512 file.
This causes policy rebuild at every install of the package.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-100.el7.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1. extract policy.30 and .policy.sha512 form the package
2. sha512sum policy.30
3. cat .policy.sha512

Actual results:
checksum is different

Expected results:
checksum is the same

Comment 1 Milos Malik 2016-11-05 08:58:26 UTC
I don't think this is a low priority bug. The fact that checksums differ (even on a freshly installed machine) effectively invalidates the pre-built policy feature:

 * http://danwalsh.livejournal.com/45712.html

Comment 2 Milos Malik 2016-11-05 09:04:57 UTC
$ ls -l selinux-policy-targeted-3.13.1-102.el7.noarch.rpm 
-rw-rw-r--. 1 mmalik mmalik 6663304 Sep 27 23:38 selinux-policy-targeted-3.13.1-102.el7.noarch.rpm
$

Following files were extracted from the above-mentioned file:

$ cat .policy.sha512 
9ff3afb7e659336993e1e7dadf41cbe7ca67b8332aed6c18b7ec711884647839fab6ba0d23771e36b640c82e1d67a19a0d6ab14eae5edddcce75527a801210b3
$ sha512sum -b policy.30 
df8f7519673877cd57ace5b97997848aa65b74d124556d269efcc42875296ee9dc2295614d954733c676d7cff59d6b87d28852b2444eccc37f4d804f00bb7564 *policy.30
$ sha512sum -t policy.30 
df8f7519673877cd57ace5b97997848aa65b74d124556d269efcc42875296ee9dc2295614d954733c676d7cff59d6b87d28852b2444eccc37f4d804f00bb7564  policy.30
$

Comment 6 Zdenek Pytela 2019-03-12 09:12:00 UTC
This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.


Note You need to log in before you can comment on or make changes to this bug.