Bug 1417644

Summary:	Regression in signature algorithm handling of Server Key Exchange messages
Product:	Red Hat Enterprise Linux 7	Reporter:	Hubert Kario <hkario>
Component:	nss	Assignee:	Daiki Ueno <dueno>
Status:	CLOSED ERRATA	QA Contact:	Hubert Kario <hkario>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	kengert, szidek
Target Milestone:	rc	Keywords:	Reproducer
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nss-3.28.3-4.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 16:50:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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):
nss-3.28.0

How reproducible:
always

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.

https://access.redhat.com/errata/RHEA-2017:1977