Bug 1997516
| Summary: | Failed to download metadata for repo 'rhui-codeready-builder-for-rhel-8-x86_64-rhui-debug-rpms' due to SSL certificate algorithm too weak | |||
|---|---|---|---|---|
| Product: | Red Hat Update Infrastructure for Cloud Providers | Reporter: | xiyuan | |
| Component: | Security | Assignee: | RHUI Bug List <rhui-bugs> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radek Bíba <rbiba> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 2.1.1 | CC: | gtanzill, tsze | |
| Target Milestone: | --- | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2001464 (view as bug list) | Environment: | ||
| Last Closed: | 2022-02-16 15:25:16 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2001464 | |||
|
Description
xiyuan
2021-08-25 12:39:55 UTC
Seems it is an upstream issue. Created ticket to google https://issuetracker.google.com/issues/197769045?pli=1 instead. Got feedback from google(seen from https://issuetracker.google.com/issues/197769045?pli=1): mo...<mo...> #3Sep 7, 2021 05:20PM Hello, I will summarize part of the investigation that has been done until today. Product team has reported that this is currently Work as Intended. RHUI (via Red Hat's implementation) is deployed using a self signed CA for the certificates between the clients and the distribution nodes. Short term plan is to not change them. These are the certs that RHUI creates and I believe they were sha1 because of RHEL 6. The Red Hat software controlled how they were created. From FIPS 140-2 Validated documentation: When your clients connect to Google infrastructure, their TLS clients must be configured to require use of secure FIPS-compliant algorithms; if the TLS client and GCP's TLS services agree on an encryption method that is incompatible with FIPS, a non-validated encryption implementation will be used. There is still an ongoing investigation about this issue and the confirmation of not declaring FIPS compliance at this level. Take into account there is no ETA for updates but we will update it shortly. Please feel free to add any other questions or information to speed up the resolution of this issue. This is has been fixed in RHUI 4.0, which is the current release This is has been fixed in RHUI 4.0, which is the current release The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |