User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:184.108.40.206) Gecko/20060613 Camino/1.0.2 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:220.127.116.11) Gecko/20060613 Camino/1.0.2 Visiting bugzilla (!) I got this dialog 3 times ina row on every page. "(null) and <sitename> can not communicate securely because they have no common encryption algorithms" Wording is not exact because I couldn't copy and paste. Reproducible: Sometimes Steps to Reproduce: 1.Visit bugzilla in camino, first time in that session. 2. 3. Actual Results: (!) I got this dialog 3 times ina row on every page. "(null) and <sitename> can not communicate securely because they have no common encryption algorithms" Wording is not exact because I couldn't copy and paste. address bar still indicated I was in a secure connection. Expected Results: Either no dialog or one, not three (I assume once for each of 3 images or something). And it shouldn't show the "secure" icon unless the wholepage is secure. A "details" button that would tell me exactly what was wrong would be a start. And it needs better error dialog handling overall.
I've run into this on one particular internal site (although it only comes up once per visit), and it prevents me from accessing it in Camino. I've been meaning to try to figure out where it comes from, since if nothing else the dialog needs to make some kind of sense.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Ah, if I visit with an older Camino I get a low-grade encryption warning, so that's at least one way to trigger the message (although that wouldn't have been the case for 1.0.2).
The "(null)" part is a regression from bug 236933 (see bug 236933 comment 71, bug 236933 comment 82, bug 236933 comment 85).
This is a dupe of bug 343837. Reporter, were you using Camino 1.0.2 when you saw these dialogs or a nightly build?
Assignee: dveditz → nobody
Oh, heh, the string change in bug 236933 just changed around the string a little; we have the same problem with branding on 1.8.0 as everywhere else, and the original string referenced branding, too. *** This bug has been marked as a duplicate of 343837 ***
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.