Evolution LDAP connection no TLS even when specified

Bug #595028 reported by Feisar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Expired
Low
Unassigned

Bug Description

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: <email address hidden>,dc=example,dc=com'

'Search base: ou=Address Book,<email address hidden>,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 <email address hidden>,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 <email address hidden>,dc=example,dc=com" method=128
slapd[7741]: conn=26 op=1 BIND <email address hidden>,dc=example,dc=com" mech=SIMPLE ssf=0

Revision history for this message
Pedro Villavicencio (pedro) wrote :

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream/GNOME . Thanks in advance!

Changed in evolution (Ubuntu):
importance: Undecided → Low
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

Changed in evolution (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in evolution (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.