Evolution Exchange Connector doesn't support self signed certificates

Bug #16667 reported by Ken Fallon
8
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

There is no option to approve selfsigned certs in Evolution Exchange connector.

To replicate
On first run of Evolution -> Selecting Server Type as Microsoft exchange and
using the url of https://x.y.com/exchange - to an exchange server using a self
signed certificate.
Pressing authenticate brings up the dialogue to enter the password.
Clicking OK just returns to the Receiving email dialogue.
The username and password (pasted from clipboard) work in firefox after
accepting the self signed cert.

I opened a ticket with Ximian some time ago on this. Here's what they say
"Here's what we think is the problem. If this is a "self signed" certificate
and it is just one level then there are many programs that will fail because it
is not truely a "Trusted Host". The certificate should be signed by a trusted
host such as Equifax or at least there needs to be another layer, not just one.
 Web browsers don't seem to care. They will let you accept the cert anyway.
This certificate signing is a configuration on the OWA/IIS server."

Revision history for this message
Rached Blili (bugzilla-dread) wrote :

I can confirm this issue. I even downloaded and added my company's certificates
to evolution's certificate store.
It's still broken. This was working fine until my company turned off
non-encrypted owa, and I can access owa just fine using a web browser.

Revision history for this message
Carthik Sharma (carthik) wrote :

Thank you for the report.

Can this bug be recreated on the current version of Evolution in Dapper? Please provide us with steps to do so. Also, please provide a debug backtrace of the crash if possible.

If this bug is not a problem anymore, please let us know so we can close the bug.

Thanks again!

Changed in evolution-exchange:
status: Unconfirmed → Needs Info
Revision history for this message
Carthik Sharma (carthik) wrote :

I am marking this bug closed as the issue seems to have been resolved by a later upload. The original reporter has not responded to a request to find if the bug still exists for 4+ weeks.

If this is still an issue for you with the latest Dapper packages, please reopen this bug, providing the required information.

Thank you for reporting this bug.

Changed in evolution-exchange:
status: Needs Info → Fix Released
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.