Ubuntu
evolution package

cannot connect with restricted cipher list

Bug #121594 reported by kieran
4
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

using evolution 2.11.4-0ubuntu1, i am unable to connect to an imap server (dovecot) over ssl which has a restricted ssl ciper list as follows 'TLSv1:!NULL:!EXP:!DES:!3DES:!MD5:!DSS'

a popup box with the error text "Server unexpectedly disconnected: Input/output error" is created.

removing the cipher list restriction from the imap server allows evolution to connect successfully.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Related to bug 82515?

Can you check on how the negotiation goes with such a session? For example, you can 'tcpdump -i <interface> -w imap.dump host <IMAP host>' , and then either run wireshark on the sniffer output, or attach it here.

No matter what, you might want to have a look at http://www.gnome.org/projects/evolution/bugs.shtml. Running with CAMEL_DEBUG=all might give us more info.

Changed in evolution:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
kieran (daralantarial) wrote :

thanks for that. it would seem evolution cannot do TLSv1 handshakes.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Sorry for the question, but did you configure your IMAP account (in Evolution) to use TLS?

In fact, what version of Evolution are you running? 2.11 seems to allow one to set TLS on IMAP (I do not really know, since I do not use IMAP). Indeed it seems yours is configured for SSL.

Revision history for this message
kieran (daralantarial) wrote :

you were correct. i had never seen the tls option previously in imap config.

i get a different error now, but it looks to be unrelated.

Revision history for this message
C de-Avillez (hggdh2) wrote :

keran, how do you want to proceed here? Is this bug done?

Revision history for this message
kieran (daralantarial) wrote :

yes, call it resolved for now.

thanks

Revision history for this message
C de-Avillez (hggdh2) wrote :

Closing not-a-bug.

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

Other bug subscribers

Remote bug watches

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