User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050519 Camino/0.8+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050519 Camino/0.8+ If https is required on the built-in web server in a Linksys router it is impossible to configure the router with Camino because Linksys apparently uses the same certificate for all their routers. Camino gives an error which says: "You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number." This seems fine, but then the only option is to click the OK button and use a different browser. Firefox gives a similar warning but allows the user to override it and accept the invalid certificate either permanently or just for the current session. Reproducible: Always Steps to Reproduce: 1. Configure the built-in web server on a Linksys router to require https. 2. Attempt to connect to the router's web server with Camino 3. Silly rabbit, there is no step 3. Actual Results: Camino refuses to allow connections to the router. Expected Results: Allow the user to override the warning and connect to the router if he or she so choosed.
i think there have been some changes to the security dialog apis that we need to make sure we stay current with.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Camino1.0
I'm experiencing the same behaviour on Mac OS X.4.2
Try with a recent build; Camino now has better cert support.
Assignee: pinkerton → sfraser_bugs
Status: ASSIGNED → NEW
Also, does this work in Firefox?
This needs re-testing with 1.0a1 or a more recent nightly branch build.
This appears to be fixed in Camino 1.0a1.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.