Bug 809817
| Summary: | syncrepl does not work with TLS | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Dario Palmisano <Dario.Palmisano> |
| Component: | openldap | Assignee: | Jan Vcelak <jvcelak> |
| Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | jsynacek, tsmetana |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-04 14:54:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Hello. Yes, we know about some problems with syncrepl and TLS. As a temporary workaround, set up Mozilla NSS certdb instead of OpenSSL cacert dir (or OpenSSL bundle cacert file). I'm closing this as a duplicate of bug 707599, because I can reproduce the same symptoms. *** This bug has been marked as a duplicate of bug 707599 *** |
Description of problem: In a red hat linux free derivative (Scientific Linux) version 6.0, I would like to configure an openldap replication (between the master ldapm.icgeb.org and the slave ldaps.icgeb.org). The syncrepl comsumer is configured as: syncrepl rid=1 starttls=critical provider="ldap://ldapm.icgeb.org:389" type=refreshAndPersist searchbase="dc=icgeb,dc=org" binddn="cn=ldapReplicator,dc=icgeb,dc=org" credentials="******" bindmethod=simple retry="20 3" when I restart the consumer, in the slave log I always get: slap_client_connect: URI=ldap://ldapm.icgeb.org:389 Error, ldap_start_tls failed (-11) However I can successfully run from the slave: ldapsearch -d 1 -x -v -D "cn=ldapReplicator,dc=icgeb,dc=org" -W -h ldapm.icgeb.org -p 389 -ZZ Below I produce, part of, the diagnostic output produced by ldapsearch command related to TLS: TLS: file ca-m.icgeb.org.crt does not end in [.0] - does not appear to be a CA certificate directory file with a properly hashed file name - skipping. TLS: loaded CA certificate file /etc/openldap/cacerts/129a25e2.0 from CA certificate directory /etc/openldap/cacerts. TLS: loaded CA certificate file /etc/openldap/cacerts/fec911d0.0 from CA certificate directory /etc/openldap/cacerts. TLS: file ldap-ldaps.icgeb.org.key does not end in [.0] - does not appear to be a CA certificate directory file with a properly hashed file name - skipping. TLS: file ldap-ldaps.icgeb.org.crt does not end in [.0] - does not appear to be a CA certificate directory file with a properly hashed file name - skipping. TLS: file ca-s.icgeb.org.crt does not end in [.0] - does not appear to be a CA certificate directory file with a properly hashed file name - skipping. TLS: certificate [E=sysadm,CN=ldapm.icgeb.org,OU=Computer Unit,O=ICGEB,ST=Italy,C=IT] is valid TLS certificate verification: subject: E=sysadm,CN=ldapm.icgeb.org,OU=Computer Unit,O=ICGEB,ST=Italy,C=IT, issuer: CN=m.icgeb.org,E=sysadm,OU=Computer Unit,O=ICGEB,L=Trieste,ST=Italy,C=IT, cipher: AES-256, security level: high, secret key bits: 256, total key bits: 256, cache hits: 0, cache misses: 0, cache not reusable: 0 Enter LDAP Password: Maybe I am wrong somewhere... Version-Release number of selected component (if applicable): openldap-2.4.23-20.el6.x86_64 openldap-devel-2.4.23-20.el6.x86_64 openldap-clients-2.4.23-20.el6.x86_64 openldap-servers-2.4.23-20.el6.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: