Closed
Bug 445500
Opened 17 years ago
Closed 17 years ago
cumbersome to add ssl exceptions.
Categories
(Camino Graveyard :: Preferences, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 398417
People
(Reporter: mkosnik+bugzilla, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.2pre) Gecko/2008071500 Camino/2.0a1pre (like Firefox/3.0.2pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.2pre) Gecko/2008071500 Camino/2.0a1pre (like Firefox/3.0.2pre)
When using Camino - I am unable to figure out how to add a SSL certificate exception - compare the message below to the behaviour of firefox3 - where links take you through the process of adding an exception. Nothing in the preferences even references "advanced encryption settings". Camino should mimic the Firefox procedures in this matter.
Reproducible: Always
Steps to Reproduce:
1. Attempt to connect to a site using a self-signed certificate.
2.
3.
Actual Results:
127.0.0.1 uses an invalid security certificate.
The certificate is not trusted because it is self signed.
(Error code: sec_error_ca_cert_invalid)
* This could be a problem with the server's configuration, or it could be someone trying to impersonate the server.
* If you have connected to this server successfully in the past, the error may be temporary, and you can try again later.
Or you can add an exception…
You should not add an exception if you are using an internet connection that you do not trust completely or if you are not used to seeing a warning for this server.
If you still wish to add an exception for this site, you can do so in your advanced encryption settings.
Expected Results:
See firefox 3 for correct behaviour - link to go through the process to add an exception.
Reporter | ||
Comment 1•17 years ago
|
||
I consider this to be is a significant regression in usability from the behaviour in Camino 1.6.1 - although I realize that "most users" will not be accessing sites with self-signed certificates.
Comment 2•17 years ago
|
||
This sure seems like a dupe of at least one other (if not several other) certificate UI bugs that are already planned for 2.0. I'll let Stuart decide which one.
Comment 3•17 years ago
|
||
(In reply to comment #0)
> I am unable to figure out how to add a SSL certificate exception
Yep, that's because at the moment you can't.
> Nothing in the preferences even references "advanced encryption settings".
Because we don't have any; when the error+exception system was added in core, they added that text as well for reasons that have never been entirely clear to me.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•