Bug 1784513 - [SLES 11sp4] [RFE] Give Satellite the ability to select if repo metadata should be signed with the key provided for rpm verification
Summary: [SLES 11sp4] [RFE] Give Satellite the ability to select if repo metadata shou...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.6.0
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On: 1410638 1589288
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-17 15:56 UTC by Mike McCune
Modified: 2024-03-25 15:34 UTC (History)
60 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1410638
Environment:
Last Closed: 2020-03-04 18:03:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike McCune 2019-12-17 15:56:06 UTC
We need to rebuild subscription-manager for SLES 11sp4 to include fixes previously delivered in prior 6.6 errata

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

Good evening,

I have a customer who is requesting the option within Satellite to sign repo metadata per STIG compliance guidelines.

I do see that repo_gpgcheck=1 is not yet supported per this related BZ:

    Bug 1360939 - Putting repo_gpgcheck=1 into yum.conf causes 404 Errors
    https://bugzilla.redhat.com/show_bug.cgi?id=1360939

However, as the customer is asking for repo metadata signing capability for Satellite software specifically, I thought it might be worthwhile to open a low-severity RFE at the very least.

Comment 5 Mike McCune 2020-03-04 18:03:15 UTC
we can close this out as it should just be tracked along with the top level RFE. We don't need this specific SLES bug anymore.

See the main RFE for tracking repo metadata signing:

https://bugzilla.redhat.com/show_bug.cgi?id=1410638

Comment 6 Red Hat Bugzilla 2023-09-18 00:19:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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