Page 1 of 1

wildards or CIDR in allow/disallow lists

Posted: Mon May 09, 2022 10:31 pm
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.

Re: wildards or CIDR in allow/disallow lists

Posted: Mon May 09, 2022 11:11 pm
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.

Re: wildards or CIDR in allow/disallow lists

Posted: Mon May 23, 2022 3:16 pm
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.)

Re: wildards or CIDR in allow/disallow lists

Posted: Sun Oct 23, 2022 9:48 pm
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.