Closed Bug 403191 Opened 18 years ago Closed 17 years ago

[Trunk] SSL certificate handling for HTTPS sites with private CAs or self-signed certs is broken

Categories

(Calendar :: Sunbird Only, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 387398

People

(Reporter: hugo-moz, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.8) Gecko/20071004 Iceweasel/2.0.0.8 (Debian-2.0.0.8-1) Build Identifier: CVS at approx 2007-11-09 12:20 UTC I have a personal website protected by a certificate signed by a CA which is not in the "default" list of certificates. Apparently, due to the changes that block access to HTTPS sites that don't have a full chain of trust to a trusted root CA, this is preventing me from syncing my calendars to that site. Firefox 3 apprently has two solutions to this issue: (a) add the root CA to the list of trusted CAs, or (b) add the certificate to the exception list. Sunbird provides no user interface for either of these two methods. This therefore prevents the above use case completely. Reproducible: Always
Assignee: dveditz → nobody
Component: Security → Sunbird Only
OS: Linux → All
QA Contact: calendar → sunbird
Hardware: PC → All
(In reply to comment #0) > Build Identifier: CVS at approx 2007-11-09 12:20 UTC Hugo, do have a Trunk or Mozilla1.8 build of Sunbird?
Hi, Martin, I think it's a trunk build, as I'm fairly sure I didn't use an -r option on checkout. Is there an easy way to check?
Hugo, you can find the version in the About dialog (Help menu!). If the version is 0.6a1, you have a Trunk build. We develop on the MOZILLA_1_8_BRANCH at the moment, and the QA team doesn't test Trunk builds. So, there may be problems and bugs, we are not aware of. If those bugs don't affect branch builds, they won't be fixed in the near future.
Summary: SSL certificate handling for HTTPS sites with private CAs or self-signed certs is broken → [Trunk] SSL certificate handling for HTTPS sites with private CAs or self-signed certs is broken
Version: unspecified → Trunk
OK, yes, it is a trunk build. It's not clear from the documentation that one should be using the MOZILLA_1_8_BRANCH to build from. I've not really built Mozilla software before, and I had assumed that, like most projects, trunk is where the action happens. I will try again with the branch.
If this is trunk only, it's still a valid bug. one day, we'll switch to trunk, and by then, this needs to get fixed.
I don't think this is a trunk only issue, we don't have certificate handling on branch either?
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.