InformAction Forums

(Tor Browser is based on FF ESR release, so 64.9.x currently, so is Quantum, so uses NoScript 11.x, not Legacy.)

therube wrote: ↑Tue Jan 21, 2020 11:39 am (Tor Browser is based on FF ESR release, so 64.9.x currently, so is Quantum, so uses NoScript 11.x, not Legacy.)

You are right in principle, but it's 68.4.1esr.

11.0.13 is released, to AMO, so is now the current version for FF (in addition to Chrome).

That said, there are no changes between 11.0.13 & the 11.0.13rc1 (which was Chrome only) except for the addition of META-INF (& immaterial change to manifest.json) which then allows an actual install in FF.

So, for FF users, simply a version number bump, if you will.
(Also allows a singular .xpi version to install in both FF & Chrome.)

This issue remains.

I will restate it in the next post.

Now, before criticising anybody, I will point out that in this thread
I 'rushed into posting', and so 'made inaccurate points'.

Here are four examples:

In the 3rd post I wrote:

DJ-Leith wrote: ↑Mon Jan 13, 2020 6:56 pm My opinion is that Giorgio intended 11.0.13rc1 to work on both Firefox and Chrome.
I speculate that he uploaded 11.0.13rc1 to AMO.

I was wrong about AMO. I had forgotten that Mozilla had stopped having 'betas on AMO'.
However, I still believe that Giorgio intends to have 'beta users on Firefox', in which case
he will need to sign the beta / rc XPI.

In the 5th post I wrote:

DJ-Leith wrote: ↑Tue Jan 14, 2020 8:49 pm

Code: Select all

8. An "Available Updates' Tab will appear on the left,

which has a typo. I meant to write: where I close the exact quotation with a 'double quote character', i.e. a ".

In the 7th post, near the end of the post, I wrote:

DJ-Leith wrote: ↑Wed Jan 15, 2020 8:11 pm Step 12 (which I did not explicitly Report) I also attempted to Update this
form 11.0.12rc2 to 'latest' (i.e. the broken 11.0.13rc1) - Failed.

I used "form" instead of "from", so I should have posted (emphasis added):
Step 12 (which I did not explicitly Report) I also attempted to Update this
from 11.0.12rc2 to 'latest' (i.e. the broken 11.0.13rc1) - Failed.

In the 15th post I said that:
"... Classic NoScript for the TOR Browser ...". This information is now out of date;
there was a time when Giorgio was having to do this (when ESR was 'not Quantum').

DJ-Leith

To restate the issue:

Issue: NoScript Updates Fail
Firefox users, on the NoScript BETA channel, when doing a 'Check for Updates'
either automatically or via "about:addons".
A 'new version' is Available but NoScript fails to Update.

The 'new version' that is 'found' is this 'unsigned version' See also

DJ-Leith wrote: ↑Thu Jan 16, 2020 3:57 pm Following up on the question:
Where do the RC / BETA versions of NoScript, for Firefox, 'check for Updates'?
... ...
It contains:

Code: Select all

"update_url": "https://secure.informaction.com/update/?v=11.0.12rc2",

This is NOT the 'Release NoScript' that is now (Feb 2020) on AMO (i.e. version 11.0.13).

Cause: the XPI is not signed

Proposed fix: Upload a signed XPI (11.0.13rc2 - or higher)
Now that the Release version is 11.0.13, I propose that the signed XPI should be
11.0.14rc1 - or higher.

Until a signed XPI is 'made available' for the 'beta channel', like this: All Firefox NoScript users, on the BETA channel, will remain at 11.0.12rc2 (or older).

Uploading a signed XPI will also fix this thread:
Unable to install Development Build 11.0.13rc1 via link on Development Build
viewtopic.php?f=7&t=25865
(which has the same cause).

The 'getit' page will also need to be updated, to reflect the proposed, signed, 11.0.14rc1 - or higher.

DJ-Leith

This seems to be fixed.

I don't know when it was fixed.
It might have been on:
"Sat, 01 Feb 2020 22:02:12 +0000"
(see the feed https://noscript.net/feed?c=200&t=a).
I can't find any better information. Note this is after my post "Sat Feb 01, 2020 4:49 pm" (just above).

Yesterday, 2020-02-11, while I was helping someone (in person) I noticed that her NoScript was now at 11.0.13rc1.
I asked another person at that location to try the test in the 1st post in this thread:
All was normal and an Update did happen. So when we did: The 'NoScript Tool Tip' also reported "11.0.13rc1" - so this is looking good.

I had previously posted:

DJ-Leith wrote: ↑Wed Jan 15, 2020 8:14 pm I also hope that even the 'blue dot' indicator 'alarm' will be solved when there is a newer working version for Firefox.
I will try and confirm that, when there is a 'new version to test'.

I am pleased to report that I have now updated Profiles from 11.0.12rc2 to 11.0.13rc1 -
using Firefox ESR (68.5.0esr), Firefox Release (73.0) and Firefox Nightly (75.0a1).
In all cases the 'normal blue dot' indicator was present, when doing the 'Check for Update',
and in all cases the NoScript Update (to 11.0.13rc1) was successful.

Regarding the thread:
Unable to install Development Build 11.0.13rc1 via link on Development Build
viewtopic.php?f=7&t=25865

I have been looking at the 'getit page',
https://noscript.net/getit, since 2020-01-13.

The only changes that I have noticed were the addition of SHA 256 links (for NoScript Classic).
So, I decided to browse direct to: (which is the URL on the getit page "Quantum" NoScript 11.0.13rc1 development build)
Doing this added NoScript 11.0.13rc1, which is what I now expected.

DJ-Leith

I am so happy that the end of the world has been postponed after all.