There is a better patch for this bug. It is already submitted upstream: http://www.openldap.org/its/index.cgi?findid=7388 +++ This bug was initially created as a clone of Bug #857373 +++ Description of problem: MozNSS certificate database in newer SQL format cannot be used. Database prefix is recognized incorrectly. Version-Release number of selected component (if applicable): openldap-2.4.32-2.fc17 How reproducible: always Steps to Reproduce: 1. certutil -d sql:/tmp/certdb -N 2. certutil -d sql:/tmp/certdb -A -n ca -t TC,, -a -i /tmp/ca.pem 3. LDAPTLS_CACERTDIR=sql:/tmp/certdb ldapsearch -x -ZZ -d1 Actual results: ... TLS: certdb config: configDir='sql:/tmp' tokenDescription='ldap(0)' certPrefix='certdb' keyPrefix='certdb' flags=readOnly TLS: cannot open certdb 'sql:/tmp', error -8018:Unknown PKCS #11 error. TLS: could not get info about the CA certificate directory sql:/tmp/certdb - error -5950:File not found. ... ldap_start_tls: Connect error (-11) additional info: TLS error -8172:Peer's certificate issuer has been marked as not trusted by the user. Expected results: ... TLS: certdb config: configDir='sql:/tmp/certdb' tokenDescription='ldap(0)' certPrefix='' keyPrefix='' flags=readOnly TLS: using moznss security dir sql:/tmp/certdb prefix . ... Additional info: Not a regression, this seems to be a problem since switching to MozNSS. --- Additional comment from jvcelak on 2012-09-14 11:00:18 CEST --- Created attachment 612778 [details] patch Upstream submission will follow. --- Additional comment from jvcelak on 2012-09-14 11:57:19 CEST --- Upstream report: http://www.openldap.org/its/index.cgi?findid=7388 --- Additional comment from updates on 2012-09-19 11:11:51 CEST --- openldap-2.4.32-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/openldap-2.4.32-3.fc17 --- Additional comment from updates on 2012-09-19 11:13:22 CEST --- openldap-2.4.32-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openldap-2.4.32-3.fc18 --- Additional comment from updates on 2012-09-20 07:58:21 CEST --- Package openldap-2.4.32-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openldap-2.4.32-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14390/openldap-2.4.32-3.fc18 then log in and leave karma (feedback).
Resolved in: openldap-2.4.33-1.fc17
openldap-2.4.33-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openldap-2.4.33-1.fc18
openldap-2.4.33-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/openldap-2.4.33-1.fc17
Package openldap-2.4.33-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openldap-2.4.33-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15910/openldap-2.4.33-1.fc18 then log in and leave karma (feedback).
openldap-2.4.33-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.