Bug 1508571

Summary:	Exporting RSA-PSS keys to PKCS#12 drops the rsa-pss identifier from them [rhel-7]
Product:	Red Hat Enterprise Linux 7	Reporter:	Alicja Kario <hkario>
Component:	nss	Assignee:	Daiki Ueno <dueno>
Status:	CLOSED ERRATA	QA Contact:	Ivan Nikolchev <inikolch>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.5	CC:	dueno, hkario, inikolch, nmavrogi
Target Milestone:	rc	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nss-3.43.0-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-06 13:08:26 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:	1645231
Bug Blocks:	1457751

Description Alicja Kario 2017-11-01 16:59:42 UTC

Description of problem:
When a private key with rsassaPss is imported from a PKCS#12 file to NSS database and later exported, the private key looses the rsassaPSS identifier, the key is exported as a regular rsaEncryption key.

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

How reproducible:
Always

Steps to Reproduce:
1. import pkcs#12 file with RSA-PSS key
2. export key to pkcs#12 file
3. inspect decrypted key 

Actual results:
rsaEncryption OID used, NULL parameters

Expected results:
rsassaPss OID used, no parameters

Additional info:

Comment 2 Simo Sorce 2019-02-11 15:39:13 UTC

This issue was not selected to be included either in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small amount of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.

Comment 14 errata-xmlrpc 2019-08-06 13:08: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://access.redhat.com/errata/RHSA-2019:2237