Bug 1533729

Summary: [RFE] certutil capability: generate CSR from orphan private key
Product: Red Hat Enterprise Linux 7 Reporter: Fraser Tweedale <ftweedal>
Component: nssAssignee: Bob Relyea <rrelyea>
Status: CLOSED ERRATA QA Contact: Ivan Nikolchev <inikolch>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.4CC: cfu, cpelland, dueno, gparente, hkario, inikolch, mharmsen, mkosek, msauton, mthacker, nmavrogi, rrelyea, szidek
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nss-3.44.0-4.el7,nss-softokn-3.44.0-5.el7,nss-util-3.44.0-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:08:28 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: 1491453    

Description Fraser Tweedale 2018-01-12 04:31:58 UTC 
(See upstream ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=430198)

Description of problem:

If you generate a with with `certutil -G`, it is not possible
using `certutil -R` to generate a CSR for it.


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


How reproducible: Always


Steps to Reproduce:
1. Generate keypair with `certutil -G`
2. Use `certutil -K` to list private keys
3. Use `certutil -R -k <key-id>` to generate a CSR for the key.

Actual results: private key cannot be located

Expected results: private key should be located when its key-id is given
as argument to `-k` option, as implied by the man page.


Additional info:
Comment 2 Fraser Tweedale 2018-01-12 04:37:21 UTC 
Patches are attached to upstream BZ: https://bugzilla.mozilla.org/show_bug.cgi?id=430198
Comment 23 errata-xmlrpc 2019-08-06 13:08:28 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