Bug 1509953

Summary:	Firefox doesn't accept server certificates with RSA-PSS signatures
Product:	Red Hat Enterprise Linux 7	Reporter:	Hubert Kario <hkario>
Component:	firefox	Assignee:	Martin Stransky <stransky>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	stransky
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-23 06:28:01 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:
Bug Depends On:	1457751
Bug Blocks:

Description Hubert Kario 2017-11-06 12:29:37 UTC

Description of problem:
When server has a certificate signed with rsa-pss algorithm, Firefox rejects it with SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED error

Version-Release number of selected component (if applicable):
nss-3.34.0-0.1.beta1.el7.x86_64
firefox-52.4.0-1.el7_4.x86_64

How reproducible:
always

Steps to Reproduce:
1. Create a regular RSA CA
2. Sign a server certificate with PKCS#1 RSASSA-PSS algorithm (certutil --pss-sign)
3. Import CA to Firefox
4. Start a server with the certificate signed in step 2.
5. Connect Firefox to the server

Actual results:
Your connection is not secure

Error code: SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED

Expected results:
Connection established, certificate accepted as valid

Additional info:
Note that support for RSA-PSS in certificates on NSS side was added in 3.34.

Comment 1 Martin Stransky 2017-11-06 12:36:16 UTC

Hm, is that something on FF side?

Comment 2 Hubert Kario 2017-11-06 15:41:33 UTC

See also reply of Brian Smith in upstream bug.

It's an issue in mozilla::pkix, and mozilla::pkix is not part of NSS.

Comment 3 Kai Engert (:kaie) (inactive account) 2017-11-28 15:30:17 UTC

According to upstream this is unlikely to happen in the RHEL 7.5 time frame. So essentially there's nothing to do for the Firefox maintainers at Red Hat, but this is rather a tracking bug for this feature becoming available. Let's at least post pone this bug to 7.6.

Comment 4 Martin Stransky 2019-08-23 06:28:01 UTC

Sorry we don't have a fix for that.

Comment 6 Martin Stransky 2019-08-23 12:14:37 UTC

As you can see the upstream bug are still open. We can have this opened for tracking purpose if you wish but don't expect it in upcoming Firefox 68 ESR rebase.