Bug 1918777

Summary:	"signature hdr data BAD" on trying to parse RPM with more than 64KB signature header
Product:	Red Hat Enterprise Linux 8	Reporter:	Patrick Uiterwijk <puiterwijk>
Component:	rpm	Assignee:	Michal Domonkos <mdomonko>
Status:	CLOSED ERRATA	QA Contact:	Jan Blazek <jblazek>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	8.3	CC:	bcotton, bfinger, jpazdziora, jwboyer, kwalker, mdomonko, mthacker, perobins
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rpm-4.14.3-11.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 14:49:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1870705

Description Patrick Uiterwijk 2021-01-21 14:31:28 UTC

Description of problem:
RPM on RHEL8 only accepts at most 64KB signature header size, contrary to the documented (upstream) 64MB size.

Version-Release number of selected component (if applicable):
rpm-4.14.3-4.el8.x86_64

How reproducible:
Consistent

Steps to Reproduce:
1. Get an RPM with a larger than 64KB
2. Run anything on that RPM that tries to parse it (rpm -Kv, rpm -ivh, dnf install)

Actual results:
error: python3-mechanize-0.4.5-4.fc34.noarch.rpm: signature hdr data: BAD, no. of bytes(19088) out of range


Expected results:
The RPM should get successfully processed.

Additional info:
This is fixed upstream to the documented behaviour by https://github.com/rpm-software-management/rpm/pull/1252 .

Acceptance Criteria:
RPM understands packages with a signature header exceeding 64KB.  This can be verified by IMA-signing a package with RPM version 4.16 (e.g. on a recent Fedora version) - that's because since 4.15, file signatures are stored in the signature header.  The test case from Bug 1896046 can be reused here.

Comment 19 errata-xmlrpc 2021-05-18 14:49:53 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 (rpm bug fix and enhancement update), 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/RHBA-2021:1606