Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
It is not possible to start selfserv with a private key and certificate stored in PKCS#11 module.

Version-Release number of selected component (if applicable):
nss-3.27.1-9.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. generate private key and certificate
2. modutil -dbdir sql:./.pki/nssdb -add nsspem -libfile libnsspem.so -string "/home/test/cert.pem;/home/test/key.pem" -force
3. selfserv -d sql:./.pki/nssdb -n cert.pem -p 4433 -V tls1.0: -H 1

Actual results:
NSS_Init failed.

Expected results:
server started, accepting TLS connections with cert.pem certificate

Additional info:
modules are initialised to Public access with PINs initialized

Hubert, is this a regression?

(In reply to Kai Engert (:kaie) from comment #3)
> Hubert, is this a regression?

I don't think so, but it would be a test blocker for proper test coverage of bug 1397979, it looks like an error on my part though, the nickname used is incorrect

The issue is caused by selfserv looking by default to the first token only. To use key in other token, a full syntax that specifies also the token name needs to be used.

The simplest way to detect that, is to tell certutil to list certificates from all tokens, in this example:

certutil -L -d sql:.pki/nssdb/ -h all

which will print:

Certificate Nickname                                         Trust Attributes
                                                             SSL,S/MIME,JAR/XPI

PEM Token #0:cert.pem                                        u,u,u


so the correct syntax to start selfserv is:
selfserv -d sql:./.pki/nssdb -n 'PEM Token #0:cert.pem' -p 4433 -V tls1.0: -H 1