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.
Bug 1238369 - NSS does not support all signature methods for Certificate Verify [rhel-7]
Summary: NSS does not support all signature methods for Certificate Verify [rhel-7]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nss
Version: 7.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Kai Engert (:kaie) (inactive account)
QA Contact: Hubert Kario
URL:
Whiteboard:
Depends On:
Blocks: 1218420 1269239 1295396 1309228
TreeView+ depends on / blocked
 
Reported: 2015-07-01 17:55 UTC by Hubert Kario
Modified: 2019-08-15 04:48 UTC (History)
8 users (show)

Fixed In Version: nss-3.21.0-14.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1269239 (view as bug list)
Environment:
Last Closed: 2016-11-04 03:55:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1179338 0 -- RESOLVED Don't require that the signature method for certificate verify is identical with PRF, support alternatives 2020-03-05 15:13:03 UTC
Red Hat Bugzilla 1212286 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1217102 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2016:2335 0 normal SHIPPED_LIVE nss bug fix update 2016-11-03 13:45:11 UTC

Internal Links: 1212286 1217102

Description Hubert Kario 2015-07-01 17:55:35 UTC
Description of problem:
NSS client can sign Certificate Verify only using SHA256 (the PRF used in ciphersuite) or SHA-1. NSS server requests signature on Certificate Verify only using SHA256 (the PRF used). This makes servers unable to interoperate with clients that can sign only using SHA-1. 

Version-Release number of selected component (if applicable):
nss-3.19.1-5.el7_1

How reproducible:
Always

Steps to Reproduce:
1. Use NSS as client or server in connections that require certificates in TLSv1.2

Actual results:
Certificate Verify always is signed using SHA-256 by NSS client
Certificate Request always asks just for RSA+SHA256, DSA+SHA256 or ECDSA+SHA256

Expected results:
most hashes listed as acceptable by server, especially DSA+SHA1 or RSA+SHA1

Additional info:

Comment 3 Hubert Kario 2015-08-12 13:42:35 UTC
This feature is necessary for interoperability between GnuTLS and NSS with TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 ciphersuite and DSA client certificates in TLSv1.2.

Comment 4 Hubert Kario 2015-09-15 17:25:33 UTC
This issue breaks communication with Microsoft Internet Explorer clients that have certificates signed with algorithms different than SHA-256.

Since the server asks only for SHA256 signatures, the client refuses to provide its certificate and aborts the connection.

This is the expected behaviour according to https://tools.ietf.org/html/rfc5246#section-7.4.4

Comment 5 Elio Maldonado Batiz 2016-01-18 15:16:26 UTC
This is one where we need to allow verification even when the digest doesn't match what was  used for the PRF. There is a similar bug for RHEL 6.8 and it should be included.

Comment 22 errata-xmlrpc 2016-11-04 03:55:26 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://rhn.redhat.com/errata/RHBA-2016-2335.html


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