InformAction Forums

There doesn't appear to be support for adding IP subnets to the whitelist, or if there is I don't know how to do it.

I've tried:

10.10.0.0/24
10.10.0.*

and the "Allow" button is greyed out for both. It only allows a complete single IP address such as 10.0.0.1. This honestly wouldn't be much of a problem, but noscript is constantly losing whitelisted addresses that I've previously added many times in the past. I believe I notice this most during FF upgrades. I'll certainly start exporting my whitelist in the future, but it will be indefinitely easier if I could add my internal networks in a few entries rather than hundreds.

If there is some way to do this now, please let me know, and if not, please let me know how to request that a feature be added.

Thanks

See if this helps, Site matching.

therube wrote:See if this helps, Site matching.

That did it. Thanks!

NoSkirt wrote:... This honestly wouldn't be much of a problem, but noscript is constantly losing whitelisted addresses that I've previously added many times in the past. I believe I notice this most during FF upgrades. ...

I've never experienced this, either on within-branch upgrades (3.6.27 to 3.6.28) or new version-bump upgrades (10.0.2 to 11.0)
This should be investigated.

You're showing 10.0.2 now, and should update to 11.0 anyway; a good time to test this. An extension conflict is quite possible.

To test:
Before upgrading, export that whitelist (or export your entire NS settings and configurations, actually -- use the Export button *at the bottom-middle of the main NS GUI*, versus *at the bottom-right of the Whitelist tab*).

Create a clean profile for your present 10.x.
Install only NoScript.
import your whitelist and/or total settings that you exported, into this clean profile.
Now upgrade to 11.0.

1) Start it with your default profile and see if you lose anything.
2) Start it with the clean profile and see if you lose anything.

If you lose stuff with the default profile but not the clean one, there's likely an extension conflict. Try combining NS with each of your other add-ons, in the clean profile, one at a time, until the culprit is isolated.

If this doesn't fix it, further investigation is warranted. This shouldn't be happening *on an overwrite upgrade in the same Firefox directory*.