Bug 111941 – yum with gpgcheck=1 installs rpms even though the gpg keys have not been imported yet

Bug 111941 - yum with gpgcheck=1 installs rpms even though the gpg keys have not been imported yet

Summary:	yum with gpgcheck=1 installs rpms even though the gpg keys have not been impo...

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	yum (Show other bugs)
Sub Component:
Version:	1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-12-11 15:08 EST by akopps
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-01-26 05:42:00 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description akopps 2003-12-11 15:08:30 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4)
Gecko/20030703

Description of problem:
I have added gpgcheck=1 in /etc/yum.conf and accidentally run
"yum update" without importing the Fedora GPG key first. Surprisingly,
yum still downloaded and installed new rpms.

Version-Release number of selected component (if applicable):
yum-2.0.4-2

How reproducible:
Always

Steps to Reproduce:
1. Remove all GPG keys from rpm data base.
2. add gpgcheck=1 to the main section in yum.conf
3. Try installing or updating packages with yum
    

Actual Results:  The update/install actions are performed.

Expected Results:  Yum should treat it as an error since gpg keys have
not been imported yet.

Additional info:

Comment 1 Jeff Johnson 2004-01-26 05:42:00 EST

Why error? For example, the rpm CLI does not treat as error.

No matter what the missing key is reported to yum. Marked upstream,
as that is where any fix will be.

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