It would be nice for NSS tools to support the following tasks to improve the usability: 1. Importing a specific certificate/private key from PKCS #12 file into NSS database. This will be useful if we do not want to use everything in the PKCS #12 file. 2. Generating a PEM file that contains a client certificate with the private key from NSS database. This can be used for client authentication on libraries that do not support NSS directly (e.g. python-requests). 3. Exporting a specific certificate/private key from NSS database into PKCS #12. This is an alternative for #2, but it will still require openssl tool to generate the PEM file. Currently the exported PKCS #12 file will include the CA certificate so it has to be removed from the PEM file in order to work with some libraries. 4. Renaming a certificate nickname in NSS database. This will be useful to clean up/organize the certificates.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
(In reply to Endi Sukma Dewata from comment #0) > 3. Exporting a specific certificate/private key from NSS database into PKCS > #12. This is an alternative for #2, but it will still require openssl tool > to generate the PEM file. Currently the exported PKCS #12 file will include > the CA certificate so it has to be removed from the PEM file in order to > work with some libraries. you mean the pk12util -o bundle.p12 -n certificate_nickname is not sufficient for them? If you have to process the p12 file with openssl, then you can easily omit the ca certificates during conversion, just use the `-clcerts` option: openssl pkcs12 -in bundle.p12 -out certificate.pem -nodes -clcerts -passin pass:pkcs12-file-password In general those are good suggestions, but NSS development happens primarily upstream, so you have a better chance of getting it fixed if you file an upstream bug. But please keep this bug open and link it to upstream bug for tracking purposes.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
issue not resolved with nss-3.25.0-1.0.fc24.x86_64
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
there was no response to Hubert's comment, and nobody has requested this upstream. Is this still in demand? Then please request upstream.
Please use more precise bug subject. Please one bug per enhancement request.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Sorry for the delay. PKI now has a PKCS #12 utility that provides some of the desired functionalities: http://pki.fedoraproject.org/wiki/PKI_PKCS12_CLI We can leave this ticket closed. Thanks.
Are you aware of this corpus of key files? https://github.com/redhat-qe-security/keyfile-corpus Or have something similar for tests? (setting needinfo to make sure you don't miss it)
I don't think we currently have such tests in PKI. The above tool is written using JSS which is a Java interface for NSS, so I suppose those PKCS #12 variations would have been covered automatically, but I'll pass it along to our team for further investigation. Thanks!