Hide Forgot
Description of problem: NSS will accept RSA PKCS#1 v1.5 signatures made using RSA-PSS keys as correct Version-Release number of selected component (if applicable): 3.34 How reproducible: always Steps to Reproduce: 1. start a server that will sign all SKEs with rsa-sha256, even if it has rsa-pss key 2. connect with tstclnt 3. Actual results: connection established Expected results: connection broken after processing SKE by client Additional info:
Hi Hubert, Since this BZ should be described in the RHEL 7.5 Release Notes, could you please fill the Doc Text using the template? I'm not sure if I would be able to use 100% accurate wording using just the first comment.
This should be fixed with the next rebase.
This issue was not selected to be included either in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small amount of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.
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-2019:2237