[Resolved] Updating from 11.0.12rc2 to 11.0.13rc1 - Failed, XPI is not signed

Bug reports and enhancement requests
DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

[Resolved] Updating from 11.0.12rc2 to 11.0.13rc1 - Failed, XPI is not signed

Post by DJ-Leith » Mon Jan 13, 2020 3:13 pm

On Windows, using Firefox 68.4.1esr, on a Profile with NoScript 11.0.12rc2

Code: Select all

1. In about:support note that NoScript is detected as "11.0.12rc2"
2. In about:addons
3. Check for Updates
4. Open a another Tab and look at about:support Note that NoScript is STILL detected as "11.0.12rc2"
Normally, the new version of NoScript would be reported.

Did NoScript Update?
Is there something missing in 11.0.13rc1?

DJ-Leith

Short summary 2020-01-20:

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 consensus includes:
* The 'NoScript you had', e.g. 11.0.12rc2, is still working.
* Firefox users will not gain any benefit from 11.0.13rc1. Either BETA 11.0.12rc2 or RELEASE 11.0.12
are the 'best versions', at this point in time, for Firefox users.
* It is possible to 'directly Install 11.0.12rc2' (see below).
* It is possible to Install 11.0.13rc1 in Waterfox Current (barbaz has)
or, if you 'bypass XPI signing checks in ESR', in Firefox 68.4.1esr (see below).

Cause: the XPI is not signed

Proposed fix: Upload a signed XPI (11.0.13rc2 - or higher)


ETA #1, on 2020-01-13, Added "- Failed" to the Subject.

ETA #2, on 2020-01-20, Added ", XPI is not signed" to the Subject.
(so that it is clearer / more obvious for Giorgio and others)
and the "Short summary 2020-01-20:".

ETA #3, on 2020-02-12, Added "[Resolved] at the start of the Subject. See also
DJ-Leith wrote:
Wed Feb 12, 2020 9:05 pm
This seems to be fixed.
I also documented tests done in that post.

DJ-Leith
Last edited by DJ-Leith on Wed Feb 12, 2020 9:09 pm, edited 3 times in total.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

User avatar
therube
Ambassador
Posts: 7636
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: Updating from 11.0.12rc2 to 11.0.13rc1

Post by therube » Mon Jan 13, 2020 5:11 pm

12rc2 is going to be the latest #development version - for FF.
(At the least, 13rc1 won't even install in FF even if you tried, as there is no /META-INF/.)

And as it is, 12rc2 is virtually identical to 13rc1, save, (insignificant) change to manifest.json, & a change to SyncMessage.js, both of which look to be Chrome specific.


(Doesn't Chrome dislike the rc# part in manifest.json? I didn't look at the actual Chrome 13rc1.)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 SeaMonkey/2.49.5

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by DJ-Leith » Mon Jan 13, 2020 6:56 pm

Thanks for confirming.
therube wrote:
Mon Jan 13, 2020 5:11 pm
12rc2 is going to be the latest version - for FF.
(At the least, 13rc1 won't even install in FF even if you tried, as there is no /META-INF/.)
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 speculate that when I did "about:addons", "Check for Updates"
a 'new version was detected'; I got the 'blue dot' indicator.

As therube found 'parts of', what a Firefox version of NoScript would normally contain, are missing.

DJ-Leith
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by DJ-Leith » Tue Jan 14, 2020 8:45 pm

This issue does affect Firefox.

I have read both threads:

Could not access Development Build on NoScript website (which is now locked)
viewtopic.php?f=7&t=25860
First post by garyf on Mon Jan 13, 2020 1:38 am

Unable to install Development Build 11.0.13rc1 via link on Development Build
viewtopic.php?f=7&t=25865
First post by garyf on Mon Jan 13, 2020 10:48 pm

I am not doubting that 11.0.13rc1 might have been uploaded /released to fix an issue with Chromium.
What I am saying is that Firefox detects a 'more recent version' and the 11.0.13rc1
is 'broken for Firefox'. In my case I have several Profiles on 11.0.12rc2.


STR

Code: Select all

1. Make new Profile for Firefox
2. Launch Firefox
Now disable automatic Extension updates.

Code: Select all

3. In "about:config", set the following:
3.1 app.update.auto false
3.2 extensions.update.autoUpdateDefault false
4. In about:preferences#general  scroll down to the "Firefox Updates" section.
In the "Allow Firefox to" sub-section select "Check for updates but let you choose to install them"
Now install a OLD Beta of NoScript.

Code: Select all

5. In a new Tab go to https://noscript.net/feed?c=200&t=a
Choose an old version of NoScript, e.g. 11.0.11rc1 from
https://secure.informaction.com/download/betas/noscript-11.0.11rc1.xpi
Now, confirm that it has installed.

Code: Select all

6. In a new Tab about:support - look in the "Extensions" section and verify that
NoScript is version "11.0.11rc1"
Continued ...
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by DJ-Leith » Tue Jan 14, 2020 8:49 pm

Now, we are going to Update it.
What would be Normal is that 'if there is a newer version' it will be Installed.

Code: Select all

7. Open a new Tab and go to about:addons, use the 'cog wheel' to "Check for Updates"
8. An "Available Updates' Tab will appear on the left,
in it will be NoScript with the 'blue dot' for Update indicator. Click this and select "Update"
So, a newer version was 'detected as being available', hence the 'blue dot' to tell you to Update.

Now, check what version we have (if 11.0.13rc1 was OK we would have jumped straight to 11.0.13rc1)

Code: Select all

9. In a new Tab about:support  - Note you are STILL on "11.0.11rc1" (or whatever OLD beta you chose).
Optional, you can Update to a more recent version MANUALLY.

Code: Select all

10. In a new Tab go to https://noscript.net/feed?c=200&t=a
Choose e.g. 11.0.12rc2
https://secure.informaction.com/download/betas/noscript-11.0.12rc2.xpi
Check to see the MANUAL Install worked:

Code: Select all

11. In a New Tab go to about:support and check that NoScript is now version "11.0.12rc2"
So, the good news is you can MANUALLY Update.
The bad news is if you now go and update this, as in steps 7-9 (above), a 'new version will be Available'
but it will NOT Install (because it is broken).

You will be 'stuck at whatever version you had', using the example of step 10, at version "11.0.12rc2".

DJ-Leith
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

User avatar
therube
Ambassador
Posts: 7636
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by therube » Wed Jan 15, 2020 1:07 am

Was thinking about this, & isn't it that there are no longer rc's on AMO?

So rc's would only update from here.

AMO shows the latest to be 11.0.12.
And if you manually install 11.0.11 from AMO, then a check for updates will bring down 11.0.12, from AMO.


Though I did put in some earlier rc, 11.0.8rc1 or whatever, & a check for updates returned nothing.
But at some point, I saw a "blue dot" (& all the while the Extensions page stated, "No updates found")?
Yet no update occurred?


What a HORRENDOUS MONSTROSITY Addons Manager has evolved into.
It has the most brain-dead UI I have ever seen.
Thinking one must either be a moron or a genius to use it.


---


https://secure.informaction.com/update/?v=11.0.11rc1 states it will try to put in 11.0.13rc1, I think?
But then no update seems to occur.
Maybe that makes sense?
But if so, it fails silently, if you will.

If it thought the update should be 11.0.12rc#, may we suppose it would in fact update?
So something wrong then with the update check?
(More on that later...)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.2 Lightning/5.8.1

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by DJ-Leith » Wed Jan 15, 2020 8:11 pm

therube wrote:
Wed Jan 15, 2020 1:07 am
Was thinking about this, & isn't it that there are no longer rc's on AMO?

So rc's would only update from here.
You may well be correct.
However, the key point in this thread is; 'Normal rc Updates Fail'.

So, when anybody, on Firefox, who is on the BETA channel, uses about:addons to 'Update Extensions'.
A 'newer version of NoScript' is 'detected'.

The check may well be to look at AMO or here; I mean one of Giorgio's sites
e.g. https://secure.informaction.com/update/

To understand this case, and the current issue, it does not matter
'where (the URL) the check was made',
what matters is a 'newer version of NoScript' was found.
In this specific case the 11.0.13rc1 was 'found' and was 'detected' as a 'newer NoScript'
(which happens to be 'broken for Firefox').

So, an 'Update was started' but it does not complete.

Another piece of good news is, I think (but don't KNOW), it seems to 'fail safely'.
I think the 'Update does not complete' and so the Profile 'still has a working NoScript':
just not the very latest BETA version.

therube wrote:
Wed Jan 15, 2020 1:07 am
But then no update seems to occur.
Maybe that makes sense?
But if so, it fails silently, if you will.
I agree with you but I also note. It is not quite silent.

A. The 'rarely used Profile' that I used for the first post in this thread, which has only
'one failed Update' (from 11.0.12rc2 to 11.0.13rc1 - Failed) still has a 'blue dot'
next to the "Available Updates" Tab (in about:addons).
I think this means 'there is one Update outstanding' (in this case the Update to 11.0.13rc1).

B. The 'new Test Profile' that I created for the 4th post (above - see this section)

Code: Select all

1. Make new Profile for Firefox
2. Launch Firefox
This Profile also had a 'blue dot' with a "2" in it.
I think this means 'there are TWO Updates outstanding'.

Remember the sequence:
Steps 7 and 8, Update from 11.0.11rc1 to 'latest' (i.e. the broken 11.0.13rc1) - Failed.
Step 10 (the MANUAL Update) was OK.
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.
So I saw the 'blue dot' with a "2" in it on Tue Jan 14, 2020.

Today, when I launch the 'new Test Profile' there is 'no blue dot' (in about:addons)
but when I repeat steps 7 and 8 (the 'normal Update procedure') it Fails (as I expect)
and there is now a 'blue dot'.

DJ-Leith
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by DJ-Leith » Wed Jan 15, 2020 8:14 pm

I hope, and expect, this issue will be solved as soon as Giorgio uploads a 11.0.13rc2
(or 'higher version') that 'works for Firefox'.

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'.


In the mean time, we are 'stuck at whatever version we had', using the example of step 10, at version "11.0.12rc2".

I am happy to remain a 'beta user': Giorgio has released more than 1,500 versions in the last 12 years and I am very grateful. Also, FYI I have not updated my other Profiles.

DJ-Leith
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

bo elam
Senior Member
Posts: 208
Joined: Sat Oct 14, 2017 2:25 am

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by bo elam » Thu Jan 16, 2020 1:36 am

I just learned about this issue. I ended up uninstalling the beta, and installed 11.0.12.

I like using the beta, are there still going to be betas in the future or not anymore?

Bo
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

User avatar
therube
Ambassador
Posts: 7636
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by therube » Thu Jan 16, 2020 1:40 am

are there still going to be betas in the future
Sure.
Just seems to be an issue ? with this particular one.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.2 Lightning/5.8.1

bo elam
Senior Member
Posts: 208
Joined: Sat Oct 14, 2017 2:25 am

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by bo elam » Thu Jan 16, 2020 7:14 am

Thanks, therube. :)

Bo
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by DJ-Leith » 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'?

I looked inside the XPI (I imagine therube also did this).

How?
I used the NoScript XPI in the 'new Test Profile' (while I was not running the Profile).
I copied "{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi" to another folder.
I used 7-Zip to unzip it into a sub-folder:
(in my case "...\Temp-look-at-NS\{73a6fe31-595d-460b-a920-fcc0f8843232}\").

I used "Notepad++.exe" to open the "manifest.json" file, in the root of the unzipped NoScript.

It contains:

Code: Select all

"update_url": "https://secure.informaction.com/update/?v=11.0.12rc2",
So this is where the 'update check is done'.
When we do a 'check for update', automatically or by 'clicking the cog wheel' (in about:addons), a 'newer version' will be found.

I think the 'broken NoScript 11.0.13rc1 .xpi' has been 'available for detection' (and download and Install) since 2020-01-13.

I still hope, and expect, this issue will be solved as soon as Giorgio uploads a 11.0.13rc2
(or 'higher version') that 'works for Firefox'.

DJ-Leith
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

barbaz
Senior Member
Posts: 9578
Joined: Sat Aug 03, 2013 5:45 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by barbaz » Thu Jan 16, 2020 6:50 pm

In case it wasn't clear yet, seems this entire issue is just that NoScript 11.0.13rc1 xpi is not signed. AFAICT there's nothing 'actually' wrong with NoScript 11.0.13rc1 xpi, it has been working fine for me in Waterfox Current.

Firefox ESR users might be able to install NoScript 11.0.13rc1 after setting about:config > xpinstall.signatures.required to false.
*Always* check the changelogs BEFORE updating that important software!
-

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed

Post by DJ-Leith » Thu Jan 16, 2020 8:06 pm

So, running Firefox 68.4.1esr, using the 'new Test Profile' that I created for the 4th post.
In "about:config" I set xpinstall.signatures.required to false

I then opened "about:addons" and attempted a 'normal Update check', as described in the 4th post.

I received the (expected Warning) with a yellow background:
"NoScript could not be verified for use in Firefox. Proceed with caution."
with a "More Information" button next to it.

Clicking the "More Information" button leads to Mozilla Support
https://support.mozilla.org/en-US/kb/ad ... =inproduct which is also to be expected.

The Update, however 'does happen' - as barbaz expected.
In the 'new Test Profile', about:support now shows "11.0.13rc1".
The NoScript 'Tool Tip', when you hover over the NoScript icon, also shows "11.0.13rc1".

Speaking for myself: I'm happy to keep my 'real Profiles' at 11.0.12rc2 - and I'm happy to test RCs / be on the BETA channel.
I speculate that Giorgio will produce a signed xpi when he has time.

I still hope, and expect, this issue will be solved for Release Firefox (72.0.1) - and newer as soon as Giorgio uploads
a 11.0.13rc2 (or 'higher version') that 'works for Firefox'.

DJ-Leith
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

DJ-Leith
Senior Member
Posts: 143
Joined: Thu Aug 04, 2011 4:23 pm

Re: Updating from 11.0.12rc2 to 11.0.13rc1 - Failed, XPI is not signed

Post by DJ-Leith » Mon Jan 20, 2020 6:49 pm

I edited the Subject of the First Post and added this Short Summary.

Short summary 2020-01-20:

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 consensus includes:
* The 'NoScript you had', e.g. 11.0.12rc2, is still working.
* Firefox users will not gain any benefit from 11.0.13rc1. Either BETA 11.0.12rc2 or RELEASE 11.0.12
are the 'best versions', at this point in time, for Firefox users.
* It is possible to 'directly Install 11.0.12rc2' (see above).
* It is possible to Install 11.0.13rc1 in Waterfox Current (barbaz has)
or, if you 'bypass XPI signing checks in ESR', in Firefox 68.4.1esr (see above).

Cause: the XPI is not signed

Proposed fix: Upload a signed XPI (11.0.13rc2 - or higher)



------

Reflections after one week, in Question and Answer format

Q1. When was this noticed and reported?
A1. Both garyf and DJ-Leith reported on 2020-01-13.
I posted because one of the things I can do, as a beta user, is give feedback.
For many years I've been on the beta NoScript (I don't automatically Update any Profile).

Q2. When was the cause discovered?
A2. It took therube less than two hours to post that the XPI was not signed.

Q3. How many people noticed?
A3. Not many. The thread had about 300 views in the first week.
More than 5% were me as I updated the thread - I've deliberately NOT been opening it;
I've just checked the Main "InformAction Forums" page viewforum.php?f=3
to see if there were more posts and getit https://noscript.net/getit to see if there is a new version.

Q4. Why so few?
A4. The 'fail to Update' is 'almost silent' (see above - the 'blue dot' discussion).
I also don't know how many Firefox users are on beta NoScript channel.

Q5. Are you sure that NoScript is working OK?
A5. To start with I was not. However, I am confident that 'all that has happened' is,
following a 'Check for Update' and finding a 'newer version', the 'updating process' failed
leaving the Profile with a working NoScript (the 'one you had'). This does illustrate that
the 'signing check' in Firefox will 'block the Install of the new XPI'; if it is not signed
(and you have not bypassed the signing check).

Q6. Why was an unsigned XPI uploaded?
A6. I don't know, I imagine it was an accident. I imagine it is hard to develop for both
Firefox and Chromium at the same time (as well as Maintaining the Classic NoScript for the TOR Browser).

Another recent example (at the end of October 2019), where (I speculate) fixing a 'Chromium issue',
led to an unexpected issue, that I am aware of is:

11.0.5rc2 Endless SPAMMING requests to sync-messages.invalid
viewtopic.php?f=10&t=25779


DJ-Leith
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Post Reply