RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "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 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 2004207 - crypto-policies blocks CHACHA20 incorrectly in openssl
Summary: crypto-policies blocks CHACHA20 incorrectly in openssl
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: crypto-policies
Version: 9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Alexander Sosedkin
QA Contact: Ondrej Moriš
Khushbu Borole
Depends On:
TreeView+ depends on / blocked
Reported: 2021-09-14 17:31 UTC by Alexander Sosedkin
Modified: 2022-05-17 16:21 UTC (History)
5 users (show)

Fixed In Version: crypto-policies-20210922-1.git6fb269b.el9
Doc Type: Bug Fix
Doc Text:
.`crypto-policies` now can disable `ChaCha20` cipher usage Previously, the `crypto-policies` package used a wrong keyword to disable the `ChaCha20` cipher in OpenSSL. Consequently, you could not disable `ChaCha20` for the TLS 1.2 protocol in OpenSSL through `crypto-policies`. With this update, the `-CHACHA20` keyword is used instead of `-CHACHA20-POLY1305`. As a result, you now can use the cryptographic policies for disabling `ChaCha20` cipher usage in OpenSSL for TLS 1.2 and TLS 1.3.
Clone Of:
Last Closed: 2022-05-17 15:54:31 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-6992 0 None None None 2022-03-29 16:26:32 UTC
Red Hat Issue Tracker RHELPLAN-97139 0 None None None 2021-09-14 17:32:38 UTC
Red Hat Product Errata RHBA-2022:3953 0 None None None 2022-05-17 15:54:41 UTC

Description Alexander Sosedkin 2021-09-14 17:31:02 UTC
Description of problem:
    crypto-policies uses `-CHACHA20-POLY1305` in openssl configs,
    which doesn't correspond to anything. `-CHACHA20` should be used instead.
    opensslcnf's Ciphersuites setting seems to correctly omit TLS_CHACHA20_POLY1305_SHA256 though

Version-Release number of selected component: crypto-policies-20210914-1.git97d08ef.el9, and all of them to date
How reproducible: always

Steps to Reproduce:
1. Disable CHACHA20 through c-p. On current 9 you can also switch to FIPS mode
2. openssl req -x509 -newkey rsa -keyout /tmp/localhost.key -out /tmp/localhost.crt -subj /CN=localhost -nodes -batch
3. openssl s_server -key /tmp/localhost.key -cert /tmp/localhost.crt -www
4. curl --insecure https://localhost:4433 | grep -i chacha

Actual results:
    TLSv1.2    :DHE-RSA-CHACHA20-POLY1305 TLSv1.2    :DHE-RSA-AES256-CCM
    TLSv1.2    :PSK-AES256-GCM-SHA384     TLSv1.2    :PSK-CHACHA20-POLY1305
    TLSv1.2    :DHE-PSK-AES256-GCM-SHA384 TLSv1.2    :DHE-PSK-CHACHA20-POLY1305

Expected results: no output

Comment 12 errata-xmlrpc 2022-05-17 15:54:31 UTC
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 (new packages: crypto-policies), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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