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:
Server rejects the CertificateVerify message signed with PKCS#1 algorithm and sha256, sha384 and sha512 hash using incorrect alert - decode_error instead of illegal_parameter
Version-Release number of selected component (if applicable):
nss-3.41.0-5.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. tlsfuzzer test-tls13-certificate-verify.py
Actual results:
check rsa_pkcs1_sha256 signature is refused ...
Error encountered while processing node <tlsfuzzer.expect.ExpectAlert object at 0x7f0457fafd90> (child: <tlsfuzzer.expect.ExpectClose object at 0x7f0457fafdd0>) with last message being: <tlslite.messages.Message object at 0x7f0456f394d0>
Error while processing
Traceback (most recent call last):
File "scripts/test-tls13-certificate-verify.py", line 583, in main
runner.run()
File "/home/hkario/dev/tlsfuzzer/tlsfuzzer/runner.py", line 227, in run
node.process(self.state, msg)
File "/home/hkario/dev/tlsfuzzer/tlsfuzzer/expect.py", line 1412, in process
raise AssertionError(problem_desc)
AssertionError: Expected alert description "illegal_parameter" does not match received "decrypt_error"
Expected results:
check rsa_pkcs1_sha256 signature is refused ...
ok
Additional info:
server does send correct alerts for SHA224, SHA1 and md5 signatures
Description of problem: Server rejects the CertificateVerify message signed with PKCS#1 algorithm and sha256, sha384 and sha512 hash using incorrect alert - decode_error instead of illegal_parameter Version-Release number of selected component (if applicable): nss-3.41.0-5.el8.x86_64 How reproducible: always Steps to Reproduce: 1. tlsfuzzer test-tls13-certificate-verify.py Actual results: check rsa_pkcs1_sha256 signature is refused ... Error encountered while processing node <tlsfuzzer.expect.ExpectAlert object at 0x7f0457fafd90> (child: <tlsfuzzer.expect.ExpectClose object at 0x7f0457fafdd0>) with last message being: <tlslite.messages.Message object at 0x7f0456f394d0> Error while processing Traceback (most recent call last): File "scripts/test-tls13-certificate-verify.py", line 583, in main runner.run() File "/home/hkario/dev/tlsfuzzer/tlsfuzzer/runner.py", line 227, in run node.process(self.state, msg) File "/home/hkario/dev/tlsfuzzer/tlsfuzzer/expect.py", line 1412, in process raise AssertionError(problem_desc) AssertionError: Expected alert description "illegal_parameter" does not match received "decrypt_error" Expected results: check rsa_pkcs1_sha256 signature is refused ... ok Additional info: server does send correct alerts for SHA224, SHA1 and md5 signatures