Public bug reported:

Binary package hint: evolution

The first time I add an LDAP directory as an address book to Evolution,
specifying TLS it will not attempt TLS.

To recreate bug:

'New address book'
'On LDAP servers'
'server.example.com'
'port: 389'
'Use secure connection: TLS'
'Login method: Use distinguished name'
'Login: cn=u...@example.com,dc=example,dc=com'

'Search base: ou=Address Book,cn=u...@example.com,dc=example,dc=com'
'Browse this book until limit reached'

After entering this information and clicking on the address book,
Evolution will ask you for your password. After entering your password
Evolution will give you this error:

"Error loading address book.
This address book cannot be opened.  This either means that an incorrect URI 
was entered, or the server is unreachable.
Detailed error message: Other error"

LDAP will log this in it's logs:
"slapd[7741]: conn=22 fd=23 ACCEPT from IP=IPA.DDR.ESS:52860 (IP=0.0.0.0:389)"
"slapd[7741]: conn=22 op=0 BIND dn="cn=u...@example.com,dc=example,dc=com" 
method=128" 
"slapd[7741]: conn=22 op=0 RESULT tag=97 err=13 text=confidentiality required"

Because, in this case, the connection _has_ to be TLS to be successful.

A combination of setting the address book to 'No encryption' then back
to 'TLS encryption' and restarting Evolution will result in Evolution
initiating a TLS connection and the LDAP directory search being
successful.

slapd[7741]: conn=26 fd=27 ACCEPT from IP=IPA.DDR.ESS:34093 (IP=0.0.0.0:389) 
slapd[7741]: conn=26 op=0 STARTTLS 
slapd[7741]: conn=26 op=0 RESULT oid= err=0 text= 
slapd[7741]: conn=26 fd=27 TLS established tls_ssf=128 ssf=128 
slapd[7741]: conn=26 op=1 BIND dn="cn=u...@example.com,dc=example,dc=com" 
method=128 
slapd[7741]: conn=26 op=1 BIND dn="cn=u...@example.com,dc=example,dc=com" 
mech=SIMPLE ssf=0

** Affects: evolution (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: contacts evolution ldap secure tls

-- 
Evolution LDAP connection no TLS even when specified
https://bugs.launchpad.net/bugs/595028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to