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 1749790 - OpenSSL advertises ed25519 and ed448 support in CertificateRequest in FIPS mode
Summary: OpenSSL advertises ed25519 and ed448 support in CertificateRequest in FIPS mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openssl
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Tomas Mraz
QA Contact: Alicja Kario
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-06 12:59 UTC by Alicja Kario
Modified: 2020-05-29 00:57 UTC (History)
0 users

Fixed In Version: openssl-1.1.1c-9.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:52:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1840 0 None None None 2020-04-28 16:52:50 UTC

Description Alicja Kario 2019-09-06 12:59:12 UTC 
Description of problem:
When the system is running in FIPS mode, OpenSSL server will still advertise support for Ed25519 and Ed448 signatures in CertificateRequest message in TLS 1.3

Version-Release number of selected component (if applicable):
openssl-1.1.1c-2.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. set up FIPS mdoe
2. openssl s_server -www -key server/key.pem -cert server/cert.pem -verify 1 -CAfile ca/cert.pem
3.PYTHONPATH=. /usr/libexec/platform-python scripts/test-tls13-certificate-request.py -k client/key.pem -c client/cert.pem -s "sha256+ecdsa sha384+ecdsa sha512+ecdsa rsa_pss_pss_sha256 rsa_pss_pss_sha384 rsa_pss_pss_sha512 rsa_pss_rsae_sha256 rsa_pss_rsae_sha384 rsa_pss_rsae_sha512 rsa_pkcs1_sha256 rsa_pkcs1_sha384 rsa_pkcs1_sha512 sha224+ecdsa rsa_pkcs1_sha224"'

Actual results:
sanity ...
OK

with certificate ...
OK

check sigalgs in cert request ...
Error encountered while processing node <tlsfuzzer.expect.ExpectCertificateRequest object at 0x7f3cbac4a5c0> (child: <tlsfuzzer.expect.ExpectCertificate object at 0x7f3cbac4a5f8>) with last message being: <tlslite.messages.Message object at 0x7f3cbac4d908>
Error while processing
Traceback (most recent call last):
  File "scripts/test-tls13-certificate-request.py", line 275, in main
    runner.run()
  File "/tmp/tmp.onwz9Qge71/tlsfuzzer/tlsfuzzer/runner.py", line 227, in run
    node.process(self.state, msg)
  File "/tmp/tmp.onwz9Qge71/tlsfuzzer/tlsfuzzer/expect.py", line 1020, in process
    self.sig_algs)
AssertionError: Unexpected sig algs. Got: [(4, 3), (5, 3), (6, 3), (8, 7), (8, 8), (8, 9), (8, 10), (8, 11), (8, 4), (8, 5), (8, 6), (4, 1), (5, 1), (6, 1), (3, 3), (3, 1)], expected: [(4, 3), (5, 3), (6, 3), (8, 9), (8, 10), (8, 11), (8, 4), (8, 5), (8, 6), (4, 1), (5, 1), (6, 1), (3, 3), (3, 1)]

sanity ...
OK

Test to verify if server accepts empty certificate messages and
advertises only expected signature algotithms in Certificate
Request message

version: 1

Test end
successful: 3
failed: 1
  'check sigalgs in cert request'

Expected results:

successful: 4
failed: 0

Additional info:
Comment 1 Tomas Mraz 2019-09-06 13:26:03 UTC 
Fortunately ed25519 or ed448 certs are not really used for now. And in RHEL-8.2 this might even become NOTABUG when ed25519 and ed448 is finally approved. However until that happens we should fix this.
Comment 7 errata-xmlrpc 2020-04-28 16:52:04 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, 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:1840
Comment 8 Fedora Update System 2020-05-29 00:57:00 UTC 
FEDORA-EPEL-2020-ff94ccbdec has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.