Re: [Security-Discuss] Invalid signature on perl-URPM-1.03-2mdk.i586.rpm

Michael Riß <[email protected]>
Newsgroups gmane.linux.mandrake.security.general
Message-ID <[email protected]>
Vincent Danen wrote:
> Yes, and it's a bogus report.  There's nothing wrong with the file.  
> Look at my comments on the report and you'll see that, unlike the poster 
> and some other people, I went through and actually *checked* to see what 
> the problem was.  And there was none.

Hello Vincent

On my machine 10.1 i586 I have these two files:

f9d5f30016da51c6afd8bbd1a7b19246  urpmi-4.5-29.1.101mdk.noarch.rpm
74faac228fb76a182ead8df7eaf3534f  perl-URPM-1.03-2mdk.i586.rpm

urpmi-4.5-29.1.101mdk.noarch.rpm is signed correctly
perl-URPM-1.03-2mdk.i586.rpm is not.

# rpm -K urpmi-4.5-29.1.101mdk.noarch.rpm
urpmi-4.5-29.1.101mdk.noarch.rpm: sha1 md5 gpg OK

# rpm -K perl-URPM-1.03-2mdk.i586.rpm
perl-URPM-1.03-2mdk.i586.rpm: (SHA1) DSA sha1 md5 gpg NOT OK

# rpm -Kv urpmi-4.5-29.1.101mdk.noarch.rpm
urpmi-4.5-29.1.101mdk.noarch.rpm:
     Header SHA1 digest: OK (76b651e16eadb02cd20a631afbd2d34727f6d8dc)
     MD5 digest: OK (d88179c2ecda8a099ea591a4f8e5cd31)
     V3 DSA signature: OK, key ID 22458a98

# rpm -Kv perl-URPM-1.03-2mdk.i586.rpm
perl-URPM-1.03-2mdk.i586.rpm:
     Header V3 DSA signature: NOKEY, key ID 26752624
     Header SHA1 digest: OK (4e2a23f8e715d734828cc63a6afaafe52d8dbf61)
     MD5 digest: OK (8b421caba12ffb32267c6110eea5b684)
     V3 DSA signature: OK, key ID 22458a98

There is the additional V3 DSA signature with key ID 26752624.
It seems to be the cooker key:
http://pgp.mit.edu:11371/pks/lookup?search=0x26752624&op=index
I guess this causes the trouble as the cooker key isn't present
on stock 10.1 machines.

cu
Michi
message.footer (text/plain, 239 B)
____________________________________________________
Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.