InformAction Forums

Good evening everyone,

Am a new member here with this being my first post...regarding the No-Script update to v2.5.7.

Normally, previous updates of No-Script have occurred automatically without any action required on my part. However, this latest update to v2.5.7...for some reason...did not occur automatically. I have updates for all extensions set to occur automatically.

I was finally able to obtain a repaired download link from Steve (aka ShyWriter) at the MBAM Forums, and have now updated to 2.5.7.

My question: Is there a particular reason the automatic update failed to occur this time, or did I somehow cause the problem?

Thank you for your time and any enlightenment!

Eagleeye wrote:... or did I somehow cause the problem?

No, I don't think you did anything wrong.
There has been a few issues, in recent days, and I can reproduce your issue.

There is a recent thread that describes a similar issue.
However, I thought the only issue was with Release Candidate (RC) versions of NoScript
(I maintain more than 20 profiles that have RC versions).

Firefox can't detect NoScript update.
http://forums.informaction.com/viewtopi ... =7&t=10141

To reproduce your issue I created a new profile and I then went to AMO to install NoScript.
https://addons.mozilla.org/en-US/firefo ... /noscript/
Here the version is still Version 2.5.6

AMO wrote:NoScript 2.5.6
by Giorgio Maone

The best security you can get in a web browser!
Allow active content to run only from sites you trust, and protect yourself against XSS and Clickjacking attacks.

So, my guess is that AMO have not yet published NoScript 2.5.7.
I also think that until they do the 'automatic Update' will not happen.

Eagleeye wrote:Normally, previous updates of No-Script have occurred automatically without any action required on my part. However, this latest update to v2.5.7...for some reason...did not occur automatically. I have updates for all extensions set to occur automatically.

I expect that when NoScript 2.5.7 is published at AMO your automatic Update will continue to work.
Eagleeye, I think - from what you posted - that you are already using 2.5.7.
So, in this case your automatic Update (of NoScript) will resume when 2.5.8 is published at AMO.

NoScript 2.5.7 is available direct from noscript.net
Please read the "Firefox can't detect NoScript update." thread (link is above).

You will read that at
Recent all builds from noscript.net (the url is in the other thread - see above)
there are links to RCs as well as Stable Releases.

Recent stable releases from noscript.net
http://noscript.net/feed
Just lists the Stable Releases.

So, if you don't want to wait for AMO you can help yourself direct.

Hope this helps

DJ-Leith

Thanks very much for the help DJ!

It seems a particular download link to obtain No-Script v2.5.7 was having problems, but subsequently were fixed...and I was finally able to download the final-release version. I've refrained from downloading beta/developmental versions of any software, primarily because if there should turn out to be some major security vulnerability in the application that results in damage to my computer...I'm not in the position of being able to just go get it fixed. (Am retired on Veterans Disability now).

Again...I really appreciate your time and the informative info/links you provided!

Best regards!

Pete C

Eagleeye wrote:Thanks very much for the help

Your welcome, glad I could help.

Your first post was nice and clear - this was very helpful.

I don't attempt to answer questions here very often.

I think in order to attempt an answer you need
A. To understand the OPs question / issue.
B. To have the time and IT resources to research the answer.
C. To be available to follow-up with further clarification.

In your case, I understood what you were asking (A) and I had recently
been investigating a similar issue (B) and so I felt I could give an
informative reply that would assist you (and others who had also
discovered that 2.5.7 was still not published at AMO).

IMHO many 'initial posts' are vague / unclear. So, those who try
and help often have to ask for clarification as the first step.

Many people seem to miss the
PLEASE READ THIS FIRST! -- FORUM RULES AND GUIDELINES

Eagleeye wrote: ... I've refrained from downloading beta/developmental versions of any software, primarily because if there should
turn out to be some major security vulnerability in the application that results in damage to my computer...I'm not in
the position of being able to just go get it fixed ...

For most software I also take this approach. However Giorgio has released more than 500 versions
of NoScript (since May 2005). He develops incrementally: fixing one or two issues in each RC.
Many of the more experienced NoScript users use the RC Versions: we get the latest security fixes.
If we ever need to 'downdate' (revert to an older Version)
we can easily do this by selecting an older version from the Recent all builds feed.

Recent all builds from noscript.net
http://noscript.net/feed?c=200&t=a

The other tip that I recommend is to backup your NoScript settings.
Noscript Options, General (Tab), Export ==> Exports all your NoScript settings.
NoScript Options, Whitelist (Tab), Export ==> Exports just your Whitelist.

You can easily Import the TXT files on another Computer or Profile.

DJ-Leith

Eagleeye wrote:...I've refrained from downloading beta/developmental versions of any software, primarily because if there should turn out to be some major security vulnerability in the application that results in damage to my computer...I'm not in the position of being able to just go get it fixed...

In the case of NS, the Dev version is the LEAST vulnerable version, not the most that you are thinking in terms of beta of software. It is the one that has had the most problems fixed and is getting to go release. Not the other way around.