Bug 1802026
| Summary: | crypto-policy FUTURE blocks communication of redhat-support-tool | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Roman Bobek <rbobek> | ||||||
| Component: | redhat-support-tool | Assignee: | Nobody <nobody> | ||||||
| Status: | CLOSED MIGRATED | QA Contact: | Supportability QE <supportability-qe> | ||||||
| Severity: | medium | Docs Contact: | Mirek Jahoda <mjahoda> | ||||||
| Priority: | unspecified | ||||||||
| Version: | 8.1 | CC: | cww, dconsoli, florianwinter, jkastnin, jrobbins, kgandhi, mjahoda, mthacker, oliver, pghole, siwinski, taziz | ||||||
| Target Milestone: | rc | Keywords: | MigratedToJIRA | ||||||
| Target Release: | 8.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||||
| Doc Text: |
.`redhat-support-tool` does not work with the `FUTURE` crypto policy
Because a cryptographic key used by a certificate on the Customer Portal API does not meet the requirements by the `FUTURE` system-wide cryptographic policy, the `redhat-support-tool` utility does not work with this policy level at the moment.
To work around this problem, use the `DEFAULT` crypto policy while connecting to the Customer Portal API.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2023-09-06 11:14:37 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: | |||||||||
| Attachments: |
|
||||||||
The FUTURE policy has a special purpose and is not meant to be used in general. It will not be adjusted because it would hinder its purpose. If the redhat-support-tool has to work with the FUTURE policy set it needs to be solved (on the server side) of the redhat-support-tool. Hello Tomas, yes, that's fine. We do not expect to change the setting of crypto policies. Can somebody from PM review this request and let us know if support-tool should work with this settings (IMHO it should). Many thanks, -Roman Basically it means that the servers that the support-tool connects to have to have 3kbit RSA certificates (or ECDSA certificates) as minimum. (There might be other issues but they are much less probable.) Created attachment 1673993 [details]
curl api output
Created attachment 1673995 [details]
curl api output - FUTURE
@vikas The certificate that is directly on the Strata pods in production is for strata.ext.us-west.dc.prod.paas.redhat.com. That certificate was renewed in June, 2019 and is 4096 bits. However, the curl that @roman face showed the following certificate was flagged: * Server certificate: * subject: C=US; ST=North Carolina; L=Raleigh; O=Red Hat, Inc.; OU=Engineering; CN=maven.repository.redhat.com * start date: Jan 13 00:00:00 2020 GMT * expire date: Jul 14 12:00:00 2020 GMT * issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=GeoTrust RSA CA 2018 * SSL certificate verify result: EE certificate key too weak (66), continuing anyway. This certificate is for the maven server that both Strata and Hydra connect to. I can't renew it since Strata doesn't own the maven server. However, the certificate expires in July so it will need to be renewed soon and the updated certificate should be 4096 bits. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
Hello all, one of our customers just reported the following issue on RHEL 8.1. Current behavior: Setting the system crypto-policy to FUTURE is blocking the communication of redhat-support-tool with Customer Portal API. --- update-crypto-policies --set FUTURE redhat-support-tool kb 66281 Please enter the password for rhn-support-rbobek: Save the password for rhn-support-rbobek in /root/.redhat-support-tool/redhat-support- tool.conf (y/n): n Problem connecting to the support services API. Is the service accessible from this host? # --- When we use some other crypto policy, the communication is working fine. The FUTURE crypto policy is very strict and probably is disabling cipher-suite needed for the communication: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening Expected behavior: redhat-support-tool should work with the FUTURE crypto policy set.