wildards or CIDR in allow/disallow lists

Ask for help about NoScript, no registration needed to post
milktree

wildards or CIDR in allow/disallow lists

Post by milktree »

I manage a few networks, all of which have a bunch of web-managed hardware (switches, routers, etc) and they're all on RFC 1918 networks.

I'm 100% sure that anything within my non-routed network is safe, and I want to allow scripts from those hosts.

Is there a way to tell noscript: "allow everything within 10.1/16" (or 10.1.0.0/16, or 10.1.*.*) CIDR notation would be ideal.

I could in theory set up DNS and allow *.mysite, but in many ways that's more work than just clicking "trusted" for each piece of hardware.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:99.0) Gecko/20100101 Firefox/99.0
barbaz
Senior Member
Posts: 10841
Joined: Sat Aug 03, 2013 5:45 pm

Re: wildards or CIDR in allow/disallow lists

Post by barbaz »

There used to be a way to do it, but it reportedly doesn't work in NoScript Webext - viewtopic.php?f=7&t=25305

I'm not aware of any other way to set entire subnets as Trusted when accessed directly by IP address.
*Always* check the changelogs BEFORE updating that important software!
-
User avatar
therube
Ambassador
Posts: 7924
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: wildards or CIDR in allow/disallow lists

Post by therube »

Aside from the /16 (which might not even be needed?), looks like 10.1 or 10.1.0 should work?
With 10.1.0 covering 10.1.0.0 ... 10.1.0.255 (& irrespective of any /#).

(I don't really have a way to test that, but looks like it should work.)
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:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.13
lh61
Posts: 1
Joined: Sun Oct 23, 2022 9:36 pm

Re: wildards or CIDR in allow/disallow lists

Post by lh61 »

therube wrote: Mon May 23, 2022 3:16 pm Aside from the /16 (which might not even be needed?), looks like 10.1 or 10.1.0 should work?
With 10.1.0 covering 10.1.0.0 ... 10.1.0.255 (& irrespective of any /#).

(I don't really have a way to test that, but looks like it should work.)
Yes, it works as you said. I just added "192.168" in the "Per-site preferences editor" and the webpages of all my LAN devices are now considered as trusted, I don't need to add them one by one to the whitelist to achieve the same result.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 Waterfox/91.3.3
Post Reply