Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In RHEL-8 we accepted SSLv2 ClientHello in openssl s_server, in RHEL-9 with openssl-3.0 server returns:
40F79F6D557F0000:error:0A000076:SSL routines:tls_choose_sigalg:no suitable signature algorithm:ssl/t1_lib.c:3281:
and we got unexpected alert on client side in tlsfuzzer - Alert(fatal, internal_error).
Version-Release number of selected component (if applicable):
openssl-3.0.0-0.alpha13.1.el9
How reproducible:
Steps to Reproduce:
1. update-crypto-policies --set LEGACY
2. openssl req -x509 -newkey rsa:2048 -keyout localhost.key -out localhost.crt -nodes -batch -subj /CN=localhost
3. wget http://download.eng.bos.redhat.com/qa/rhts/lookaside/tlslite/tlsfuzzer-0.0.0-alpha37.tar.gz
4. tar xzf tlsfuzzer-0.0.0-alpha37.tar.gz
5. openssl s_server -www -key localhost.key -cert localhost.crt 2>server.err >server.out &
6. PYTHONPATH=tlsfuzzer /usr/bin/python tlsfuzzer/scripts/test-sslv2hello-protocol.py -d "SSLv2 Client Hello"
Actual results:
SSLv2 Client Hello ...
Error encountered while processing node <tlsfuzzer.expect.ExpectServerHello object at 0x7fc6b205d400> (child: <tlsfuzzer.expect.ExpectCertificate object at 0x7fc6b205d430>) with last message being: <tlslite.messages.Message object at 0x7fc6b2065610>
Error while processing
Traceback (most recent call last):
File "/tmp/tmp.xhz2aEYVpe/tlsfuzzer/scripts/test-sslv2hello-protocol.py", line 325, in main
runner.run()
File "/tmp/tmp.xhz2aEYVpe/tlsfuzzer/tlsfuzzer/runner.py", line 220, in run
raise AssertionError("Unexpected message from peer: " +
AssertionError: Unexpected message from peer: Alert(fatal, internal_error)
server.err:
40F79F6D557F0000:error:0A000076:SSL routines:tls_choose_sigalg:no suitable signature algorithm:ssl/t1_lib.c:3281:
Additional info:
I am actually not sure if SSLv2 CH should be accepted on RHEL-9 or not.
Actually, I misunderstood the question, I thought that the issue was with DEFAULT policy, not LEGACY policy.
Since LEGACY policy is expected to enable support for SHA-1, connections that use SSLv2 ClientHello are expected to work on RHEL-9.
The bug is that SECLEVEL=1 does not enable SHA-1: bug 1959016
*** This bug has been marked as a duplicate of bug 1959016 ***