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.
DescriptionKai Engert (:kaie) (inactive account)
2013-08-02 15:49:19 UTC
Regarding the /etc/pki/nssdb directory:
- nss installs cert8+key3
- nss-sysinit installs cert9+key4
At coolkey.rpm installation time, a %post scriplet installs the coolkey pkcs#11 module into the default module, which is secmod.db
However, coolkey isn't registered into the new pkcs11.txt file used by the newer shared-db sql access mechanism.
I propose that coolkey registers itself into both places:
* I propose to change the existing scriptlet, which will use the default
access mechanism, to explicitly spell out the dbm: access mechanism
* I propose to add calls that will explicitly register itself using the
sql: access mechanism.
Comment 1Kai Engert (:kaie) (inactive account)
2013-08-02 15:54:39 UTC
Comment 4Kai Engert (:kaie) (inactive account)
2013-08-02 17:04:21 UTC
Thanks for the r+
Will you take care of getting it checked in to RHEL 6.5 git, as part of your other coolkey related work?
Second question, what about other branches? Should this get cloned for RHEL 7 at least?
(In reply to Kai Engert (:kaie) from comment #4)
> Second question, what about other branches? Should this get cloned for RHEL
> 7 at least?
I have a test case that reproduces the problem, so if it is present on RHEL 7 I'll clone the bug.
Small update: can't test if the problem is present on RHEL 7 as removing coolkey package doesn't unregister the module from pkcs11.txt file, see bug 1017252
Hubert, bug 1017252 is the same issue. This bug is clearly fixed in the current 6.5 coolkey build. I think this bug just needs to be added to the errata, but I think it needs a QA ack for that.
bob
Comment 11Kai Engert (:kaie) (inactive account)
2013-10-14 21:10:07 UTC
Bob, I want to doublecheck, as you used a slightly different patch.
For the "sql" database check, you used
modutil -dbdir sdb:%{nssdb}
I had expected you to use sql:
Did you intentionnally use sdb: ?
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.
http://rhn.redhat.com/errata/RHBA-2013-1699.html