Bug 78657
Summary: | RFE: Support for OpenPGP v4 signatures used by SuSE. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ralf Corsepius <corsepiu> | ||||
Component: | rpm | Assignee: | Paul Nasrat <nobody+pnasrat> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 8.0 | CC: | barryn, michael | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-06-07 21:29:15 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Ralf Corsepius
2002-11-27 05:09:59 UTC
This is true for only certain types of RPMs. For instance, on my system - I built fetchmail 6.1.0-1 from a Red Hat SRPM. I receive the following: $ rpm -q -vv --queryformat '%{siggpg:armor}' -p /usr/src/redhat/RPMS/i686/fetchmail-6.1.0-1.i686.rpm D: Expected size: 540239 = lead(96)+sigs(180)+pad(4)+data(539959) D: Actual size: 540239 D: /usr/src/redhat/RPMS/i686/fetchmail-6.1.0-1.i686.rpm: MD5 digest: OK (e3e1fc770d75b7fe642c13975fe0b62b) (not base64) However, if I run the query on a third-party RPM: $ rpm -q -vv --queryformat '%{siggpg:armor}' -p /usr/download/mplayer-0.90pre8-1.i686.rpm D: Expected size: 908223 = lead(96)+sigs(248)+pad(0)+data(907879) D: Actual size: 908223 warning: only V3 signatures can be verified, skipping V4 signature Segmentation fault Yet, IBM's Java runtime environment RPM seems to be okay as well: $ rpm -q -vv --queryformat '%{siggpg:armor}' -p /usr/download/IBMJava2-JRE-1.3.1-1.0.i386.rpm D: Expected size: 19038112 = lead(96)+sigs(100)+pad(4)+data(19037912) D: Actual size: 19038080 D: /usr/download/IBMJava2-JRE-1.3.1-1.0.i386.rpm: MD5 digest: OK (ecd5caf5547eb1ae166b15c3cae65629) (not base64) I checked to see what type of RPM the aforementioned packages were: $ file /usr/src/redhat/RPMS/i686/fetchmail-6.1.0-1.i686.rpm fetchmail-6.1.0-1.i686.rpm: RPM v3 bin i386 fetchmail-6.1.0-1 $ file /usr/download/mplayer-0.90pre8-1.i686.rpm mplayer-0.90pre8-1.i686.rpm: RPM v3 bin i386 mplayer-0.90pre8-1 $ file /usr/download/IBMJava2-JRE-1.3.1-1.0.i386.rpm IBMJava2-JRE-1.3.1-1.0.i386.rpm: RPM v3 bin i386 IBMJava2-JRE-1.3.1-1.0 All RPM v3, right? So... ... attachment of strace of query on mplayer package next ... Created attachment 86664 [details]
strace of rpm query to mplayer package
Can you supply a pointer to the package with the OpenPGP v4 signature packaet? That'll help me get the segfault fixed pronot. Thanks. I think I downloaded mplayer from the main mplayer website. I'll submit an attachment later on (don't have it on this workstation). A pointer i(i.e. URL) rather than attachment please, there's a size limit for bugzilla attachments. And thanks for the help. Note: My initial report was referring to original RH-8.0 packages. Wrt: V4 sigs: Any SuSE-8.0/SuSE-8.1 package will do ftp://ftp.suse.com/pub/suse/i386/8.1/suse WORKSFORME with rpm-4.2: bash$ rpm -Kvv ~/TODO/bash-2.05b-47.i586.rpm D: Expected size: 629864 = lead(96)+sigs(188)+pad(4)+data(629576) D: Actual size: 629832 only V3 signatures can be verified, skipping V4 signature /home/devel/jbj/TODO/bash-2.05b-47.i586.rpm: MD5 digest: OK (2376c1ed552591501c8216725b1b27be) The segfault was (my guess) fixed in the "official" rpm-4.1 release. Try rpm-4.1-9 packages at ftp://people.redhat.com/test-4.1. Summary changed to get OpenPGP v4 signatures implemented. Additional patches from Suse for v4 signatures are in rpm HEAD / rpm 4.4.x branch I believe it should all be working there. Closing. Please file a new bug or raise discussion on rpm-devel list https://lists.dulug.duke.edu/mailman/listinfo/rpm-devel if you still have an issue. |