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:
rpm cannot parse some RPMs, failing with
error: mono-addon-core-2.6.7-6.1.x86_64.rpm: rpmReadSignature failed: sigh load: BAD

This is due to rpm-4.8.x-region-size.patch introduced in 4.8.0-19.el6_2.1. Removing this patch and rebuilding rpm makes it work again.


Version-Release number of selected component (if applicable):
rpm-4.8.0-19.el6_2.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. rpm -Kp http://ftp.novell.com/pub/mono/download-stable/RHEL_5/x86_64/mono-addon-core-2.6.7-6.1.x86_64.rpm
  
Actual results:
error: mono-addon-core-2.6.7-6.1.x86_64.rpm: rpmReadSignature failed: sigh load: BAD


Expected results:
mono-addon-core-2.6.7-6.1.x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#7e2e3b05)

Those mono packages have a slightly malformed signature header, which rpm prioer to the recent security fixes didn't notice. The exact issue is that the signature header of those packages contain alignment for data types which are not supposed to be aligned, causing the expected vs calculated size to mismatch.

As the "regular" header in these packages doesn't seem to have the bogus alignments, perhaps they are being signed with some modified rpm version or other custom code that aligns all data whereas rpm only expects alignment on int16, int32 and int64 data types.

The bottom line is that the packages are buggy and Novell needs to fix them (or rather, the process used to sign them). It's been reported at least here: https://bugzilla.novell.com/show_bug.cgi?id=756827