Empathy ignores "remember this choice for future connections" on untrusted certificate error dialogue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
empathy (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When starting Empathy, if it tries to connect to servers that present untrusted certificates (in particular self-signed as with Gmail or Facebook), there is a check box to ask Empathy to remember the action for next time. However setting that check box has no effect.
Steps to reproduce:
1. Start empathy with a Gmail of Facebook account;
2. The untrusted certificate dialogue appears (see screen shot);
3. Click on the "remember this choice for future connections" check box;
4. Click "Continue";
5. Close Empathy (go offline or log out);
6. Restart Empathy.
Expected behaviour
Empathy should connect to the account without popping up the untrusted certificate dialogue.
Actual behaviour:
Empathy presents the untrusted certificate dialogue again despite the user request to remember the previous action.
Note: I completely understand that untrusted certificates are a security risk and that users should be notified. However, when it happens all the time on well know services, ignoring user requests to remember the action will eventually lead users to ignore that type of warnings and click through anyway.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: empathy 3.1.92-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 27 21:41:06 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: empathy
UpgradeStatus: Upgraded to oneiric on 2011-09-14 (12 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #821619, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.