InformAction Forums

Helpful suggestions are requested, and will be received with gratitude, rather than attitude.

Maybe I made a mistake. I "Removed" NoScript from my Firefox Add-ons. It was v2.6.8.35, and yet, when I clkd on Check for Updates using Firefox/Add-ons Manager/Extensions, including NoScript v2.6.8.35 along with my ~13 other Extensions + 2 Plugins, the search reported, No updates found. Now, I cannot get NoScript downloaded.
I had not used this Mac (OS X 10.7.5), since Apple's Security Update #2014-004 was installed, last Saturday night. [N.B. - - The Security Update 2014-004 is not, it appears, for patching the "Shellshock" bug, for neither of the two CVE reports applicable to Shellshock was cited in its supporting info, Apple KB HT1222, this afternoon. Apple Software Update reported No new software, when checked an hour or two ago.]
When I tried to get NoScript v2.6.8.43 from the big, green Install button on the webpage showing noscript.net in the browser's location slot, Firefox first put down a small tab below the bookmarks bar, saying approx. "Firefox prevented this site (noscript.net) from asking you to install software on your computer." so I clkd on the button labelled, "Allow". The tab changed to say, "The add-on could not be downloaded because of a connection failure on noscript.net." A little further exploring work-arounds produced a security glitch page, and expanding the "Technical details" on that page revealed that Firefox had this complaint:
" noscript.net uses an invalid security certificate.
" The certificate is not trusted because no issuer chain was provided. The certificate is only valid for ariel.informaction.com
" The certificate expired on 4/6/13 8:32 PM. The current time is 9/30/14 4:22 AM.
(Error code: sec_error_unknown_issuer),"
A similar result came out when I tried to get NoScript via addons.mozilla.org, only, the tab cited that domain, and when I pushed into the security glitch, it named the mozilla domain as the source of the errors.

Comedy of Errors? Not so funny.

Is this behavior, now repeated about a dozen times tonight, the expected thing? Is there an about:config key that I can fix, for a workaround. I never had this problem before Apple Security Update 2014-004,or with Firefox v2.6.8.43 on my Windows 8 machine. No problems with updating Extensions in Firefox on my Mac. until tonight.

Helpful suggestions are requested, and will be received with gratitude, rather than attitude.

Does this page work for you?

(Apple made changes on their end, such that, for a time, & until Mozilla put in a fix on their end, even FF users were unable to update from 32.0.1 to 32.0.2 kind of thing. Wonder if that applies here...?)

RxDDude wrote:I "Removed" NoScript from my Firefox Add-ons. It was v2.6.8.35, and yet, when I clkd on Check for Updates using Firefox/Add-ons Manager/Extensions, including NoScript v2.6.8.35

Wait, what? How can you check for updates to NoScript via the Add-ons Manager if you deinstalled NoScript?

As another Mac OS X Lion user, I can tell you that until I upgraded from SeaMonkey 2.28 (like Firefox 31) to SeaMonkey 2.29.1 (like Firefox 32.0.3), I had to click on many XPIs twice to get them to download, and even then I had to be careful what I did or the XPI wouldn't install and the UI would be totally messed up...

Delete Firefox.app and reinstall from a fresh .dmg of Firefox 32.0.3. (If you can't connect via that https link, try changing the protocol to http or ftp.) Then, if that doesn't fix it...

Another possibility might be to try to use the "Save Link As" context menu entry, then drag the NoScript add-on you downloaded into the Firefox window. I know that's not a good solution but does that work?

Does NoScript (or any other https served file, for that matter) download fine in a clean profile?

EDIT Worst case scenario, do you have a full Time Machine system backup from before these issues started?
EDIT2 Just updated NS dev build, and had to click the link twice, so actually looks like that issue is not totally fixed in SeaMonkey 2.29.1. But I did see it work a few times before where it didn't in 2.28, weird...