Bug 63301 - unknown signatures aren't warned
unknown signatures aren't warned
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
: Security
Depends On:
  Show dependency treegraph
Reported: 2002-04-12 02:10 EDT by Chris Ricker
Modified: 2015-01-07 18:55 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-12 14:51:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2002-04-12 02:10:13 EDT
up2date appears to be ignoring GPG signatures which it can't understand.

When downloading packages which are unsiqned it warns.  However, when
downloading packages signed with a signature it doesn't recognize (such as the
beta RPMs signed with the beta key), it downloads and installs them without
generating any warnings.
Comment 1 Adrian Likins 2002-04-12 14:22:11 EDT
The beta gpg key should be on the new default keyring
(/etc/sysconfig/rhn/up2date-keyring.gpg), so the key
is known.
Comment 2 Chris Ricker 2002-04-12 14:27:21 EDT
It doesn't appear to be, at least judging by the failed checks seen from rpm
--checksig against the new packages
Comment 3 Adrian Likins 2002-04-12 14:51:37 EDT
rpm doesnt use the up2date keyring by default, so you will
need to add the key to roots keyring (or whatever keyring
you use to validate rpms with).

try `gpg --import /usr/share/rhn/BETA-RPM-GPG-KEY`
and then verifing the package...

Comment 4 Chris Ricker 2002-04-12 22:23:16 EDT
Ah, I was thinking rpm would already have the keys.  I'll close this then, since
everything works as it should after I add the keys to the user running rpm.
Comment 5 Bill Peck 2003-05-27 11:27:57 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


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