Description of problem: We would like to use SECMOD_OpenUserDB() and SECMOD_CloseUserDB() in OpenLDAP to maintain multiple MozNSS cert DBs. But SECMOD_CloseUserDB() always fails with SEC_ERROR_UNKNOWN_PKCS11_ERROR. I'm attaching simple reproducer which initializes the context, opens the user DB, closes it and shuts the context down. The function flow is following: - SECMOD_CloseUserDB() - secmod_UserDBOp() - PK11_CreateNewObject() - NSC_CreateObject() - sftk_CreateNewSlot() at pkcs11.c:4001 returns CKR_ATTRIBUTE_VALUE_INVALID at pkcs11.c:3884 Version-Release number of selected component (if applicable): nss-3.13.4-3.fc17.x86_64 How reproducible: always with the reproducer Steps to Reproduce: 1. tar xf userdb-open-close.tgz && cd userdb-open-close/ 2. make 3. ./userdb certdb Actual results: SECMOD_CloseUserDB(): -8018 (Unknown PKCS #11 error.) NSS_ShutdownContext(): -8053 (NSS could not shutdown. Objects are still in use.) Expected results: Everything OK. Additional info:
Created attachment 592941 [details] reproducer
Jan, I noticed that the reproducer uses the legacy databse format. Does it make any difference if the shared db (sqlite based) is used?
No it doesn't, if I did it correctly: $ mkdir -p /tmp/sqlcertdb $ certutil -d sql:/tmp/sqlcertdb -N Enter a password which will be used to encrypt your keys. The password should be at least 8 characters long, and should contain at least one non-alphabetic character. Enter new password: Re-enter password: $ ls /tmp/sqlcertdb cert9.db key4.db pkcs11.txt $ ./userdb sql:/tmp/sqlcertdb SECMOD_CloseUserDB(): -8018 (Unknown PKCS #11 error.) NSS_ShutdownContext(): -8053 (NSS could not shutdown. Objects are still in use.) $
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.