Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1687673 - RFE: GPG CA keys
Summary: RFE: GPG CA keys
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: yum
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.2
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-12 06:24 UTC by Karel Srot
Modified: 2019-03-22 06:51 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 662712
Last Closed:
Type: Feature Request
Target Upstream Version:

Attachments (Terms of Use)

Description Karel Srot 2019-03-12 06:24:58 UTC
This feature introduced in RHEL-6.1 is not available in yum4/dnf. We need to evaluate whether we should implemented.

see all comments in bug 662712 for additional details.

+++ This bug was initially created as a clone of Bug #662712 +++

This apparently never made it into a BZ, so trying to dump my email into one now (sorry PM and QA :o)

Description of problem:
 * yum - Add ability to specify (per repo) a "CA" key used to validate downloaded gpg keys.

- the right thing to do is to have yum and rpm support x509 signatures, 
 with the ability to do revocation (crl or timestamps or both) and even do 
 them as detached from the rpm.
 But this isn't plausible for 6.1, it'll need to be worked on in Fedora 
 upstream for some time and is definately not a RHEL 6.x feature.


 So we came up with an 
 alternative that we think will work for 6.1, be backwards compatible, and 
 much easier to implement.  Please correct this if it's not quite as we 
 - the repo files specify a single gpg key url pointing to remote URL (just 
 as it does currently)
 - where CA certificates are being used, when yum goes to get that remote 
 url it will also attempt to grab the same url with ".sig" (or similar) 
 appended, a detached signature of the key (*1)
 - yum checks that the file it downloaded is valid and that the detached 
 signature was signed by the specified channel 'CA' (some local key file), 
 if so it imports that key without prompting.

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