Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
an issue with both Satellite and CDN in that they don't currently support the 'FUTURE' protocols defined in RHEL 8 system-wide crypto policy.
Customer required the disabling of SHA1 based protocols, which 'FUTURE' achieves [1].
Satellite defaults to a 2048 key size. RHEL8 'FUTURE' requires 3071 bit minimum.
# echo | openssl s_client -connect satellite.example.com:443 2>/dev/null | openssl x509 -text -noout | grep 'Public-Key'
RSA Public-Key: (2048 bit)
# update-crypto-policies --set FUTURE
Setting system policy to FUTURE
# yum repolist
Updating Subscription Management repositories.
Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 0.0 B/s | 0 B 00:01
Error: Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-rpms'
Setting back to 'DEFAULT' works:
root[~] # update-crypto-policies --set DEFAULT
Setting system policy to DEFAULT
root[~] # yum repolist
Updating Subscription Management repositories.
Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 879 B/s | 4.5 kB 00:05
Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 1.1 MB/s | 8.7 MB 00:08
Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 763 B/s | 4.0 kB 00:05
repo id repo name status
rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 5,771
rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 2,097
[1] https://www.redhat.com/en/blog/consistent-security-crypto-policies-red-hat-enterprise-linux-8
For the scope of this RFE, it is expected that
- as a user, I can regenerate the certificates with a new key length
- as a user, I can regenerate the certificates for my capsules.
- new installs of Satellite should use a longer key length.
(In reply to Rich Jerrido from comment #0)
Hello
I have verified that the certificates used for the default install of Satellite 6.8 and Satellite Capsule 6.8 use a 4096 bit key.
>
> For the scope of this RFE, it is expected that
>
> - as a user, I can regenerate the certificates with a new key length
> - as a user, I can regenerate the certificates for my capsules.
Note that I tested the above steps as root user
> - new installs of Satellite should use a longer key length.
This is now 4096
Thank you
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4366
an issue with both Satellite and CDN in that they don't currently support the 'FUTURE' protocols defined in RHEL 8 system-wide crypto policy. Customer required the disabling of SHA1 based protocols, which 'FUTURE' achieves [1]. Satellite defaults to a 2048 key size. RHEL8 'FUTURE' requires 3071 bit minimum. # echo | openssl s_client -connect satellite.example.com:443 2>/dev/null | openssl x509 -text -noout | grep 'Public-Key' RSA Public-Key: (2048 bit) # update-crypto-policies --set FUTURE Setting system policy to FUTURE # yum repolist Updating Subscription Management repositories. Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 0.0 B/s | 0 B 00:01 Error: Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-rpms' Setting back to 'DEFAULT' works: root[~] # update-crypto-policies --set DEFAULT Setting system policy to DEFAULT root[~] # yum repolist Updating Subscription Management repositories. Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 879 B/s | 4.5 kB 00:05 Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 1.1 MB/s | 8.7 MB 00:08 Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 763 B/s | 4.0 kB 00:05 repo id repo name status rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 5,771 rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 2,097 [1] https://www.redhat.com/en/blog/consistent-security-crypto-policies-red-hat-enterprise-linux-8 For the scope of this RFE, it is expected that - as a user, I can regenerate the certificates with a new key length - as a user, I can regenerate the certificates for my capsules. - new installs of Satellite should use a longer key length.