Red Hat Bugzilla – Bug 991515
Coolkey not registered in /etc/pki/nssdb/pkcs11.txt
Last modified: 2013-11-21 18:05:56 EST
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.
Created attachment 782034 [details] patch v1 possible fix, can you please review?
Comment on attachment 782034 [details] patch v1 r+
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
Works fine on RHEL 6.5.
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: ?
erratta updated.
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