Bug 63301

Summary:	unknown signatures aren't warned
Product:	[Retired] Red Hat Linux	Reporter:	Chris Ricker <chris.ricker>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED ERRATA	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	gafton, mihai.ibanescu, srevivo
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-04-12 18:51:43 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:

Description Chris Ricker 2002-04-12 06:10:13 UTC

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 18:22:11 UTC

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 18:27:21 UTC

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 18:51:37 UTC

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-13 02:23:16 UTC

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 15:27:57 UTC

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.

http://rhn.redhat.com/errata/RHSA-2003-177.html