[addressbook] impossible to connect to TLS/SSL LDAP server on port 636

Bug #751868 reported by Mathieu Trudel-Lapierre
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Fix Released
Medium
Mathieu Trudel-Lapierre

Bug Description

Binary package hint: evolution

With the latest commits from git in evolution (included in evolution 2.32.2), LDAP over port 636 (SSL or TLS) appears to fail to connect properly if the addressbook entry was created in evolution 2.32.2 (but works for "migrated" connections), with errors such as:

Invalid query
Cannot authenticate user

etc.

Turns out reverting commit 8542059ec53e51f56ddc4b4ad720739ec075c72a solves the issue -- newly created addressbook entries in evolution can then successfully connect.

Related branches

Changed in evolution (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package evolution - 2.32.2-0ubuntu5

---------------
evolution (2.32.2-0ubuntu5) natty; urgency=low

  [ Mathieu Trudel-Lapierre ]
  * debian/patches/99_git_ldaps_on_port_636_f0ac225.patch: Revert commit
    8542059: it breaks connection to servers that allow only SSL, not TLS.
    (LP: #751868)
 -- Didier Roche <email address hidden> Fri, 08 Apr 2011 11:00:47 +0200

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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