Bug 1417644 - Regression in signature algorithm handling of Server Key Exchange messages
Summary: Regression in signature algorithm handling of Server Key Exchange messages
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nss
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Daiki Ueno
QA Contact: Hubert Kario
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-30 13:51 UTC by Hubert Kario
Modified: 2017-08-01 16:50 UTC (History)
2 users (show)

Fixed In Version: nss-3.28.3-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-01 16:50:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1334114 0 None None None 2017-01-30 13:51:56 UTC
Red Hat Product Errata RHEA-2017:1977 0 normal SHIPPED_LIVE nss bug fix and enhancement update 2017-08-01 17:57:47 UTC

Description Hubert Kario 2017-01-30 13:51:56 UTC
Description of problem:
NSS 3.28 server that has only ECDSA certificate with P-384 curve will not sign Server Key Exchange message with SHA-256 if client advertises support only for SHA-1 and SHA-256 ECDSA signatures

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Setup NSS server with P-384 curve
2. Connect with client advertising P-256 and P-384 curves as well as SHA-256+ECDSA signature only

Actual results:
connection aborted

Expected results:
Connection established

Additional info:
This is caused by applying TLSv1.3 semantics to the Signature Algorithms extension even when the connection negotiated TLSv1.2 protocol.

Comment 2 Kai Engert (:kaie) (inactive account) 2017-01-30 15:47:28 UTC
Upstream confirmed a minimal fix is sufficient, which changes a bool parameter.

See the upstream bug for the patch.

Comment 7 errata-xmlrpc 2017-08-01 16:50:07 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.


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