by Mad_Man_Moon » Thu May 28, 2020 11:18 pm
Reporting back.
------------------------- All images are in a pixhost gallery than can be downloaded as a zip if needs be.
Just quickly, I have a feeling that this whole issue might actually be affecting others, but they're either describing it differently, or noticing different symptoms of the same incident, or not noticing it at all ... yet. Maybe I'm just unlucky!
(
-- at myself )
It should also be noted that of course I'm not angry or anything, and hopefully none of this reads this way, I'm just trying to provide as much information as I possibly can to assist with any ongoing issues ... if there are any.
I do not feel entitled to anyone's time, nor do I expect any response. That said, if this looks like there could be a small bug somewhere, it might help to just let folks know, so we can ensure that we don't change anything important in trying to fix it ourselves and make things even worst.
Or just tell me I'm screwed or stupid ... I can handle it !
EDIT:
Have been updating, and I'm thinking that Android is basically ok, but will get with ft beta since I think sync might not work on ff standard ... works in old nightly on Android, will update later.
Basically, I think I need to test with the laptop to do anything worthwhile.
-----------
Forethought
So, I had a bunch of thoughts where this might have been coming from which all got thrown in the air by the Android FF client. It's admittedly outdated, but it's working fine. With no Sync.
Previously I thought it was looking like it wasn't related to that ... now I've forgotten my own name ... cats and dogs are living together ... mass hysteria!
If stuff definitively points to a Firefox issue, I'll look in to raising it with them, but I really wouldn't know where to start. However at least I'll have gathered the data.
Before I go on, the only thing that
I've changed that *could* be a contributing factor might be the xpinstall flags. I will test with that turned back to "true" on all builds, but I doubt it's the cause. I will attempt to change that back, and come back with the first edit to this post to report.
-----------
References
First up, all the versions of FF get NS immediately, and very soon after I import a NS data file from my base install (
full fat, not just the sites). As a future test, I'll attempt to overwrite this, and/or try it on a fresh build.
All versions currently have XPI flags at false.
OK, I'll reference some different versions/builds of FF during this, so I guess I should map those out, my Windows and Android are not bleeding edge latest versions, but they're latest enough to be getting the annoying crap that has come with those in the past couple of years
.
- WDSB - Win10 Desktop Standard Base - Firefox 76.0.1 64-bit - NS 11.0.26
Sync and a single standard profile. This is my longstanding FF install, my home if you will, the one that all others came from. I'd prefer to be using Nightly (for ... reasons) but won't use either until I know what's going on with this.
- WDN - Win10 Desktop Nightly - FFN 76.0.1 64-bit - NS 11.0.26
Sync and a single standard profile. This is the stand-alone download of nightly that I've been running up until this point. I didn't use the MSI, and should have, I've installed the MSI ready for migration, but haven't opened yet. This is a version or two behind.
- AFS - Android FF Standard - FF 68.5.0 (latest is 68.8.1) - NS 11.0.26
No sync, single standard profile installed. This is the standard Firefox on Android.
- AFN - Android FF Nightly - FFN 200514 (Build #2015740211) - NS 11.0.26
This has sync turned on, and the one profile. I've only just started using this, so it's very much stock.
I have a W10 laptop, too, but I've not turned that on to test as yet, will bring it in if I can.
-----------
Details
I've put a basic CSV of this information on shrib here, remove the spaces:
https : / / shrib . com / # noscript Csv Stuff
But now that URL is up there I guess anyone can edit it!
Win10 Desktop Standard Base
Looking at WDSB there are the capability.policy.maonoscript.sites and noscript.untrusted config flags, this is the only build that still has those. I think it's clear, though, that it's completely ignoring the untrusted list ... or so it seems.
Here's an image of the Per-site Permissions (PsP), which are drastically short for close to 15 years of building:
- NOPE NS SPAM GUARD STRIKES AGAIN
That whole list is about 130 which is roughly 10% of the untrusted list alone, let alone the trusted sites.
It is clearly not showing anything from the noscript.untrusted list, of which I'll put the first 7 here to match the PsP amount shown:
Code: Select all
will be edited in, I think it was causing the spam filter to spasm
Those should be the first 7 entries on that list.
I had a side note about whether this was related to the yellow site label issue, but that appears to be resolved in the upcoming release candidate. Deleted a paragraph here, ignore subsequent mentions of the yellow issue. I thought it maybe all tied together I'm silly!
Anyway ... I will not be attempting to click or whitelist anything on this build, because I don't want to lose any of that, to be honest. I guess I can try some stuff, but only if asked by bigwigs . Basically I'm expensive.
This version also has a noscript.filterXExceptions flag, amongst other stuff (like my old ABE rules ) the details are at the end of this (long) post.
The xpinstall.signatures.required and xpinstall.whitelist.required flags are set to "false" on this build, but it was pointless and I couldn't add the XPI I wanted to, so my first test will be to turn that back on.
Add-ons:
- Facebook Container 2.1.1
- Firefox Multi-Account Containers 6.2.5 (yes on top of the nightly version, there was functionality missing)
- Greasemonkey 4.9
- HTTPS Everywhere 2020.5.20 (but currently turned off)
- Startpage.com 1.3.0
- uBlock Origin 1.27.6
... and disconnect is disabled.
NoScript flags available:
- will enter later for spam
Win10 Desktop Nightly
So on to Nightly, and this was where I first started to notice it. Actually it was initially when I was "pronning", that I realised that I'd definitely had to whitelist these sites before. Pronning is a serious business, people.
There were no NS flags at all here, and it's certainly not showing anything that I'd previously put in the list, plus the yellow thing is happening here, too.
This build is pretty bare. But it does have the same Add-Ons as the main one:
- Facebook Container 2.1.1
- Firefox Multi-Account Containers 6.2.5 (yes on top of the nightly version, there was functionality missing)
- Greasemonkey 4.9
- HTTPS Everywhere 2020.3.16
- Startpage.com 1.3.0
- uBlock Origin 1.27.0
... and disconnect is disabled.
There are NoScript config flags available.
Android FF Standard
This is the only unsynced version of FF that I have ... and it ... ... it *might* be OK? So maybe it is the sync ... or something I'm syncing ... oh for chrissakes.
Yep, it is working, but it's also the only version of FF that isn't generally up to date. Sure the silly WDN is mentally off version wise, but this is 3 versions old now of the main release.
Have updated, will test again in a second. but I think I tested it either side of an update and it worked. The problem is that I can't get sync to work at all on this version ... it could be because sync is disabled in this version. Will install beta and see if sync works there.
Anyway, it's fine I think ... tested on that hub ... yes that one. I'll add testing post update of this to the list.
Add-ons:
- Activate Reader View 0.1.2
- Default (theme) 1.00
- HTTPS Everywhere 2020.5.20
- Startpage.com 1.1.4
- uBlock Origin 1.27.6
There are NoScript config flags available.
Android FF Nightly
It seems to save settings with sync turned on. Only HTTPS otherwise.
Android sync only does passwords/logins, bookmarks, and history, though.
Nightly Version
Code: Select all
Nightly 200514 06:00 (Build #2015740211)
42.0.20200513162226, 956bc5f9b
GV: 78.0a1-20200513094918
AS: 0.58.2
Add-ons:
- HTTPS Everywhere 2020.5.20
There are NoScript config flags available.[/color]
-----------
Future tests
Hopefully I'll test the following, but I'm not doing this to any schedule, or even professionally, just adhoc, really, when I pick the device up.
- Test the affect of the xpinstall flags back to true.
(probably nil)
- Update AFF and test.
- Test sync to see if it syncs the NS data.
(i didn't think it would, but i'll check that a recent update hasn't changed that)
- Test importing the NS data file fresh on each.
- Test uBlock Origin interference, it is a new addition to my daily usage to get some ABE like functionality.
(probably nil)
- Test Greasemonkey interference on WDSB only.
- Laptop - Standard Firefox - Sync & Multi Profile
- Laptop - Firefox Nightly - Sync & Standard Profile
- Nvidia Shield Tablet K1 - Standard Firefox - No Sync/Profile
- Maybe test the 2017 Amazon Fire HD8 fresh, it's got no FF, but it's a frickin' Fire tablet it'll probably just die
Reporting back. 8-)
[i]------------------------- All images are in [url=https://pixhost.to/gallery/V7Klz]a pixhost gallery[/url] than can be downloaded as a zip if needs be.[/i]
Just quickly, I have a feeling that this whole issue might actually be affecting others, but they're either describing it differently, or noticing different symptoms of the same incident, or not noticing it at all ... yet. Maybe I'm just unlucky! :lol: ( :roll: [i]-- at myself[/i] )
It should also be noted that of course I'm not angry or anything, and hopefully none of this reads this way, I'm just trying to provide as much information as I possibly can to assist with any ongoing issues ... if there are any.
I do not feel entitled to anyone's time, nor do I expect any response. That said, if this looks like there could be a small bug somewhere, it might help to just let folks know, so we can ensure that we don't change anything important in trying to fix it ourselves and make things even worst. :lol:
Or just tell me I'm screwed or stupid ... I can handle it ! :lol:
EDIT:
Have been updating, and I'm thinking that Android is basically ok, but will get with ft beta since I think sync might not work on ff standard ... works in old nightly on Android, will update later.
Basically, I think I need to test with the laptop to do anything worthwhile. 😩
-----------
[b][i][u]Forethought[/u][/i][/b]
So, I had a bunch of thoughts where this might have been coming from which all got thrown in the air by the Android FF client. It's admittedly outdated, but it's working fine. With no Sync.
Previously I thought it was looking like it wasn't related to that ... now I've forgotten my own name ... cats and dogs are living together ... mass hysteria!
If stuff definitively points to a Firefox issue, I'll look in to raising it with them, but I really wouldn't know where to start. However at least I'll have gathered the data.
Before I go on, the only thing that [i]I've[/i] changed that *could* be a contributing factor might be the xpinstall flags. I will test with that turned back to "true" on all builds, but I doubt it's the cause. I will attempt to change that back, and come back with the first edit to this post to report.
-----------
[b][i][u]References[/u][/i][/b]
First up, all the versions of FF get NS immediately, and very soon after I import a NS data file from my base install ([i]full fat, not just the sites[/i]). As a future test, I'll attempt to overwrite this, and/or try it on a fresh build.
All versions currently have XPI flags at false.
OK, I'll reference some different versions/builds of FF during this, so I guess I should map those out, my Windows and Android are not bleeding edge latest versions, but they're latest enough to be getting the annoying crap that has come with those in the past couple of years ;).
[list][*][color=#0040FF][b][i]WDSB[/i] - Win10 Desktop Standard Base[/b] - [u]Firefox 76.0.1 64-bit - NS 11.0.26[/u][/color]
Sync and a single standard profile. This is my longstanding FF install, my [i]home[/i] if you will, the one that all others came from. I'd prefer to be using Nightly ([i]for ... reasons[/i]) but won't use either until I know what's going on with this.
[*][color=#008040][b][i]WDN[/i] - Win10 Desktop Nightly[/b] - [u]FFN 76.0.1 64-bit - NS 11.0.26[/u][/color]
Sync and a single standard profile. This is the stand-alone download of nightly that I've been running up until this point. I didn't use the MSI, and should have, I've installed the MSI ready for migration, but haven't opened yet. This is a version or two behind.
[*][color=#FF0000][b][i]AFS[/i] - Android FF Standard[/b] - [u]FF 68.5.0 ([i]latest is 68.8.1[/i]) - NS 11.0.26[/u][/color]
No sync, single standard profile installed. This is the standard Firefox on Android.
[*][color=#FF00FF][b][i]AFN[/i] - Android FF Nightly[/b] - [u]FFN 200514 (Build #2015740211) - NS 11.0.26[/u] [/color]
This has sync turned on, and the one profile. I've only just started using this, so it's very much stock.[/list]
[i]I have a W10 laptop, too, but I've not turned that on to test as yet, will bring it in if I can.[/i]
-----------
[b][i][u]Details[/u][/i][/b]
I've put a basic CSV of this information on shrib here, remove the spaces:
https : / / shrib . com / # noscript Csv Stuff
But now that URL is up there I guess anyone can edit it! :oops:
[color=#0040FF][b][i]Win10 Desktop Standard Base[/i][/b]
Looking at [b][i]WDSB[/i][/b] there are the [u]capability.policy.maonoscript.sites[/u] and [u]noscript.untrusted[/u] config flags, this is the [i]only[/i] build that still has those. I think it's clear, though, that it's completely ignoring the untrusted list ... or so it seems. ;)
Here's an image of the Per-site Permissions (PsP), which are drastically short for close to 15 years of building:
[list][*][i]NOPE [/i]NS SPAM GUARD STRIKES AGAIN :lol: [/list]
That whole list is about 130 which is roughly 10% of the untrusted list [i]alone[/i], let alone the trusted sites.
It is clearly not showing anything from the [u]noscript.untrusted[/u] list, of which I'll put the first 7 here to match the PsP amount shown:[/color]
[code]will be edited in, I think it was causing the spam filter to spasm[/code]
[color=#0040FF]Those should be the first 7 entries on that list.
I had a side note about whether this was related to the yellow site label issue, but that appears to be resolved in the upcoming release candidate. Deleted a paragraph here, ignore subsequent mentions of the yellow issue. I thought it maybe all tied together I'm silly!
Anyway ... I will not be attempting to click or whitelist anything on this build, because I don't want to lose any of that, to be honest. I guess I can try some stuff, but only if asked by bigwigs ;). Basically I'm expensive.
This version also has a [u]noscript.filterXExceptions[/u] flag, amongst other stuff ([i]like my old ABE rules[/i] :D ) the details are at the end of this ([i]long[/i]) post.
The [u]xpinstall.signatures.required[/u] and [u]xpinstall.whitelist.required[/u] flags are set to "false" on this build, but it was pointless and I couldn't add the XPI I wanted to, so my first test will be to turn that back on.
Add-ons:
[list][*]Facebook Container 2.1.1
[*]Firefox Multi-Account Containers 6.2.5 ([i]yes on top of the nightly version, there was functionality missing[/i])
[*]Greasemonkey 4.9
[*]HTTPS Everywhere 2020.5.20 ([i]but currently turned off[/i])
[*]Startpage.com 1.3.0
[*]uBlock Origin 1.27.6[/list]
... and disconnect is disabled.
NoScript flags available:
[list][*]will enter later for spam[/list][/color]
[color=#008040][b][i]Win10 Desktop Nightly[/i][/b]
So on to Nightly, and this was where I first started to notice it. Actually it was initially when I was "[i]pronning[/i]", that I realised that I'd definitely had to whitelist these sites before. Pronning is a serious business, people.
There were no NS flags at all here, and it's certainly not showing anything that I'd previously put in the list, plus the yellow thing is happening here, too.
This build is pretty bare. But it does have the same Add-Ons as the main one:
[list][*]Facebook Container 2.1.1
[*]Firefox Multi-Account Containers 6.2.5 ([i]yes on top of the nightly version, there was functionality missing[/i])
[*]Greasemonkey 4.9
[*]HTTPS Everywhere [i]2020.3.16[/i]
[*]Startpage.com 1.3.0
[*]uBlock Origin [i]1.27.0[/i][/list]
... and disconnect is disabled.
There are NoScript config flags available.[/color]
[color=#FF0000][b][i]Android FF Standard[/i][/b]
[s]This is the only unsynced version of FF that I have ... and it ... ... it *might* be OK? So maybe it is the sync ... or something I'm syncing ... oh for chrissakes.[/s]
Yep, it is working, but it's also the only version of FF that isn't generally up to date. Sure the silly WDN is mentally off version wise, but this is 3 versions old now of the main release.
Have updated, will test again in a second. but I think I tested it either side of an update and it worked. The problem is that I can't get sync to work at all on this version ... it could be because sync is disabled in this version. Will install beta and see if sync works there.
Anyway, it's fine I think ... tested on that hub ... yes that one. I'll add testing post update of this to the list.
Add-ons:
[list][*]Activate Reader View 0.1.2
[*]Default (theme) 1.00
[*]HTTPS Everywhere 2020.5.20
[*]Startpage.com 1.1.4
[*]uBlock Origin 1.27.6[/list]
There are NoScript config flags available.[/color]
[color=#FF00FF][b][i]Android FF Nightly[/i][/b]
It seems to save settings with sync turned on. Only HTTPS otherwise.
Android sync only does passwords/logins, bookmarks, and history, though.
Nightly Version
[code]Nightly 200514 06:00 (Build #2015740211)
42.0.20200513162226, 956bc5f9b
GV: 78.0a1-20200513094918
AS: 0.58.2[/code]
Add-ons:
[list][*]HTTPS Everywhere 2020.5.20[/list]
There are NoScript config flags available.[/color]
-----------
[b][i][u]Future tests[/u][/i][/b]
Hopefully I'll test the following, but I'm not doing this to any schedule, or even professionally, just adhoc, really, when I pick the device up.
[list=1][*]Test the affect of the xpinstall flags back to true.
([i]probably nil[/i])
[*]Update AFF and test.
[*]Test sync to see if it syncs the NS data.
([i]i didn't think it would, but i'll check that a recent update hasn't changed that[/i])
[*]Test importing the NS data file fresh on each.
[*]Test uBlock Origin interference, it is a new addition to my daily usage to get some ABE like functionality.
([i]probably nil[/i])
[*]Test Greasemonkey interference on [b][i]WDSB[/i][/b] only.
[*]Laptop - Standard Firefox - Sync & Multi Profile
[*]Laptop - Firefox Nightly - Sync & Standard Profile
[*]Nvidia Shield Tablet K1 - Standard Firefox - No Sync/Profile
[*][i]Maybe test the 2017 Amazon Fire HD8 fresh, it's got no FF, but it's a frickin' Fire tablet it'll probably just die :lol: [/i][/list]