Bug 1417644 – Regression in signature algorithm handling of Server Key Exchange messages

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1417644 - Regression in signature algorithm handling of Server Key Exchange messages

Summary:	Regression in signature algorithm handling of Server Key Exchange messages

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	nss (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Daiki Ueno
QA Contact:	Hubert Kario
Docs Contact:

URL:
Whiteboard:
Keywords:	Reproducer

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-01-30 08:51 EST by Hubert Kario
Modified:	2017-08-01 12:50 EDT (History)
CC List:	2 users (show)

See Also:
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 12:50:07 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Mozilla Foundation	1334114	None	None	None	2017-01-30 08:51 EST
Red Hat Product Errata	RHEA-2017:1977	normal	SHIPPED_LIVE	nss bug fix and enhancement update	2017-08-01 13:57:47 EDT

Groups: None (edit)

Description Hubert Kario 2017-01-30 08:51:56 EST

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 10:47:28 EST

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 12:50:07 EDT

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

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