GNOME Bugzilla – Bug 440316
Improve SSL Certificate check bad signature dialog
Last modified: 2012-04-05 12:36:41 UTC
While checking my mail today, I was presented with a dialog containing some cryptic text, which asked me to accept....something. As-is, I don't think that this is a usable dialog, because no person who is not reasonably familiar with SSL will understand this dialog. Even as a developer myself, I'm not 100% sure what the issue is just from the dialog presented. Additionally, the options of OK and Cancel don't really make sense in this context. Suggestions: Split the issue into 3 parts. 1) Clearly state at the beginning what the problem is. "The SSL Certificate for mail.foo.org is bad." The idea is to summarize what the issue is in simple language (though having jargon like SSL and Certificate may be necessary). 2) Have a few (short) suggestions of what this could mean to the user, so that they know why they're clicking Accept or Reject or whatever and what their acceptance or rejectitude means to them. 3) At the bottom, have a GtkExpander with "Details" that give the SSL cert mess that's currently in the dialog. Other information:
Created attachment 88570 [details] Screenshot of the current dialog.
*** Bug 605773 has been marked as a duplicate of this bug. ***
Created attachment 201428 [details] [review] eds patch for evolution-data-server; This changes API to be able to provide custom buttons into camel_session_alert_user(). I didn't increase Camel's API version, because it is already increased. This also adds temporary trust level, which is relevant only till reload of the camel cert database. Warning message text was also changed to: SSL Certificate for '%s' is not trusted. Do you wish to accept it? Detailed information about the certificate: .... [Reject] [Accept temporarily] [Accept permanently] The thing is that the API allows only text messages, thus there cannot be added any active widget into the content area of the warning dialogue. This also saves database whenever the bad certificate is encountered, to be sure that user's choice is saved properly.
Created attachment 201429 [details] [review] evo patch for evolution; To properly manage the changed API.
Created commit 287ea88 in eds master (3.3.2+) Created commit d03f8df in evo master (3.3.2+)
*** Bug 666150 has been marked as a duplicate of this bug. ***