This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira ( 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 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 "RHEL project" in Red Hat Jira (issue links are of type "", 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.
Bug 1802026 - crypto-policy FUTURE blocks communication of redhat-support-tool [NEEDINFO]
Summary: crypto-policy FUTURE blocks communication of redhat-support-tool
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: redhat-support-tool
Version: 8.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Nobody
QA Contact: Supportability QE
Mirek Jahoda
Depends On:
TreeView+ depends on / blocked
Reported: 2020-02-12 08:30 UTC by Roman Bobek
Modified: 2023-09-08 06:00 UTC (History)
12 users (show)

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.
Clone Of:
Last Closed: 2023-09-06 11:14:37 UTC
Type: Bug
Target Upstream Version:
oliver: needinfo? (vrathee)

Attachments (Terms of Use)
curl api output (12.73 KB, application/xml)
2020-03-27 08:34 UTC, Roman Bobek
no flags Details
curl api output - FUTURE (3.83 KB, text/plain)
2020-03-27 09:02 UTC, Roman Bobek
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-2345 0 None Migrated None 2023-09-08 06:00:36 UTC

Description Roman Bobek 2020-02-12 08:30:25 UTC
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:

Expected behavior:
redhat-support-tool should work with the FUTURE crypto policy set.

Comment 1 Tomas Mraz 2020-02-12 10:42:09 UTC
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.

Comment 2 Roman Bobek 2020-02-19 08:54:46 UTC
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,


Comment 3 Tomas Mraz 2020-02-19 09:44:25 UTC
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.)

Comment 20 Roman Bobek 2020-03-27 08:34:56 UTC
Created attachment 1673993 [details]
curl api output

Comment 22 Roman Bobek 2020-03-27 09:02:49 UTC
Created attachment 1673995 [details]
curl api output - FUTURE

Comment 23 Jim Robbins 2020-03-27 17:17:42 UTC

The certificate that is directly on the Strata pods in production is for 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;
*  start date: Jan 13 00:00:00 2020 GMT
*  expire date: Jul 14 12:00:00 2020 GMT
*  issuer: C=US; O=DigiCert Inc;; 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.

Comment 53 RHEL Program Management 2023-09-06 11:09:32 UTC
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.

Comment 54 RHEL Program Management 2023-09-06 11:14:37 UTC
This BZ has been automatically migrated to the 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 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.

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