663792 - Firefox Nightly fails to find updates because aus3.mozilla.org uses an untrusted certificate

Status: RESOLVED DUPLICATE of bug 663801

(AUS Graveyard :: General, defect)

Description

[Bill Gianopoulos [:WG9s]]

I am not sure why more people don;t see this.  It did, however, only occur on one of my computers, because all of the others seem to have because of other browsing already have the "Thawte SSL CA" certificate added to the list of trusted root certificates.

In any event with a fresh install and a new profile, so that only the build-in root CAs are trusted, nightly builds will fail to find updates because they don't trust the certificate used by aus3.mozilla.org.

The easiest way to fix this would be to have the aus3.mozilla.org servers return the "Thawte SSL CA" certificate as part of the certificate chain.  Since that certificate is issued by a CA that whose trust is built-in to Mozilla.products, that owuld be sufficient to resolve the issue.

Comment 1

[Bill Gianopoulos [:WG9s]]

Attachment: Thawte SSL CA certificate

For others encountering this issue, as a workaround, you can import this attachment as a trusted root CA.  It is not necessary to check any of the trust check-boxes in the resultant pop-up.

Comment 2

[WildcatRay]

(In reply to comment #1)
> Created attachment 538875 [details]
> Thawte SSL CA certificate
> 
> For others encountering this issue, as a workaround, you can import this
> attachment as a trusted root CA.  It is not necessary to check any of the
> trust check-boxes in the resultant pop-up.

For those who may not know, it is Tools > Options > Advanced > Encryption > View Certificates.

BTW-That did it for me. Thanks, Bill

Comment 3

[solcroft]

As far as I can tell, this bug affects every channel of Firefox, not just nightly.

Comment 4

[Alexander L. Slovesnik]

Should be fixed in Bug 663801

Comment 5

[Bill Gianopoulos [:WG9s]]

(In reply to comment #3)
> As far as I can tell, this bug affects every channel of Firefox, not just
> nightly.

This would have effected every channel that was using the new aus3.mozilla.org update server.  I have no idea which channels that effected other than nightly.

Comment 6

[the-edmeister]

Aurora 6.0a2 was affected, too. But no problem with 4.0.2pre. Strange thing is that all three use the aus3.mozilla.org server, but only two were having  a problem - since June 9th or 10th for me.