Closed Bug 445957 Opened 16 years ago Closed 16 years ago

Add-ons doesn't work well in firefox3.0.

Categories

(addons.mozilla.org Graveyard :: API, defect)

x86
Solaris
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: guoye36, Unassigned)

Details

Steps to Perform:
   1. Go to Tools -> Add-ons.
   2. Click the "Browse All Addons" link.
Expected result:
It should open another browser window to UMO (a page at http://addons.mozilla.org/). 

Actual result:
After step 1, a warning message popped up:
services.addons.mozilla.org:443 uses an invalid security certificate. 
The certificate will not be valid until 12/08/07 05:23.
(Error code: sec_error_expired_certificate).

And after step 2, There is none response.
It was found on solaris_nevada_93&jds_nevada_95 installed on X86 .
This seems to be something wrong with addons.mozilla.org's certificate setup or your configuration. Is your computer's clock actually correct?
Component: Extension/Theme Manager → API
Product: Firefox → addons.mozilla.org
QA Contact: extension.manager → api
Target Milestone: Firefox 3 → ---
Version: 3.0 Branch → 3.2
Since there was no response and I just ran through the steps to reproduce with no problems I'm marking this worksforme.  If there's still a problem feel free to add more info.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
i had this bug, and it was not working.

what made it work: adding manually services.addons.mozilla.org
and addons.mozilla.org to the advanced / encryption / view certificates / add exception

I previously had ff1.5 installed with certificate set to 'ask every time' and most root certificates DELETED. (sorry i don't trust TURKTRUST, AOL, GO DADDY and whatnot. If i want a secure connection with www.mybank.com i check their certificate, and if it looks cool, and my location url is correct, i accept it.
also have turned of the certificate checking mechanism, because i don't trust the so called 'trusted' truste and above organizations.

In fact right now I deleted several of them.
WHY every certificate has to be manually deleted?? and cannot select all of these 'authorities' to delete them in one step??
anyway, as in firefox 1.5, in ff3.0 after deleting them, THEY COME BACK! 
#%$#@! what's the point having manually deleted the whole list took an hour!!!

anyway:
I think this issue: my error gives slightly different:
services.addons.mozilla.org:443 uses an invalid security certificate.
The certificate is not trusted because the issuer certificate is not trusted.
(Error code: sec_error_untrusted_issuer)

is related to the fact that mozilla seems to be validated by equifax secure, and i might have deleted their certificate in my firefox 1.5 installation.

Another thing that bugged me: I installed 3.0 by uninstalling 1.5 first, then deleting all of the directory in program files/mozzila firefox but STILL it managed to install 3.0 including all the extentions i had in 1.5

appearently the addons/extentions are situated in documents and settings folder and NOT uninstalled when uninstalling 1.5... i find that pretty unacceptable to have an uninstallment leaving these kind of possibly dangerous traces!

although i am happy most things work in 3.0 now as they did in 1.5 (passwords addons, history, bookmarks, etc) i wish i was ASKED for this at uninstalling firefox!

looking forward to your reaction.
Johnathan, is there anything we need to do to investigate this more or is this just because P deleted the root certs?
Ye Guo's problem is almost certainly a bad clock (his Firefox is saying in 2008 that a cert which goes live 12/08/07 is not yet valid, which is not true in 2008, regardless of any potential for misconfiguration on AMO's end).

As for P - yes, if he deleted the root that issues AMO's cert, it will be indistinguishable from a forgery and PSM will punt.  If he wants to receive updates, he should re-enable that root.  His other complaints sound like different bugs, to me.
P, the problems you describe are not related to this bug. The fact that, if you
delete the respective certificate authority root cert from your install,
services.AMO won't work without re-adding the certificate is expected behavior.

Regarding the bulk deletion of certificates, you probably want to file an
enhancement request in "Core :: Security: PSM".

Your enhancement request about Firefox's profile folder location also has
nothing to do with AMO, you may want to file a bug in the "Core :: Profile:
BackEnd" component of Bugzilla.

Please, in the future, make sure to file issues in at least somehow the right
components, and also ensure to file different issues in different bugs.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.