InformAction Forums

I'm trying to do a rather mundane thing: Stream shared video from a remote library on the plex.tv media streaming website.

Remote libraries are HTTP servers that are accessed with their IP address with requests to URLs like http://93.x.x.x:32400/. Since they are private machines they regularly get assigned new IP addresses. Consequence: Even though manually allowing them in NoScript works, doing that doesn't make a whole lot of sense.

The ABE rule that should do the right thing is trivial:
Yet, it does not work: The plex.tv website loads, but access to the remote library does not.

Cross-check: This immediately blocks the entire Plex site:
So ABE is enabled and I'm doing something wrong. Thanks for your help!

does any advices from viewtopic.php?f=7&t=19589 help you?

oh, and if you need to match arbitrary ipv4 address in your abe rule, try

Thanks, makes sense. I've tried this, in the SYSTEM block:
and less specific:
both with no success.

Again: My intent is to use ABE to avoid being forced to allow individual IP addresses in NoScript. The hosts in question are not on my LAN, they get a new IP every 24 hours. Manually white-listing them every day is pointless.

If I interpret the ABE FAQ correctly, this is not possible. ABE rules do not override NoScript rules and you have to enable stuff in NoScript before ABE even gets to see it. Is that correct?

May I see any message starting with "[ABE" which you can find in your Browser Console (Ctrl+Shift+J) when this happens?

I would love to, but there are no ABE messages in the browser console.

There are loads of Plex related debug messages, nothing from ABE. For good measure I've even enabled the legacy devtools.errorconsole.enabled Firefox preference and ticked "Chrome and Addon debugging" in the console settings. No change.

NoScript version is 2.6.8.43, Firefox version is 32.0.3.

Oh, you mean SCRIPT allowing. No, that can't be accomplished via ABE, as it's a totally separate part of the NoScript add-on.
If the IPv4 addresses are truly arbitrary, there is no solution other than "Allow Scripts Globally" (maybe "Allow HTTPS scripts globally on HTTPS documents" will do if all the URLs are https?) or cascading permissions mode.
If it's not quite arbitrary, see if http://noscript.net/features#sitematching helps you at all?

Yes, I meant script allowing. In the meantime, I figured from the FAQ that it wasn't possible. Though it really would have been nice. *sighs*

"Allow scripts globally" is not an option, under these circumstances I could just as well remove NoScript entirely.

Well then I'm back at clicking "allow temporarily" every time I want to use the remote library. I'll look into creating a ranged sitematch in NoScript, maybe that helps somewhat. I think I can take it from here. Thanks!

Did you try the 'cascade permissions' mode as barbaz suggested?

It's tempting to do that.

The point is... My reason for running NoScript is to be able to select what kinds of widgets, trackers and whatnot should be allowed to run in any given page, with the default being "none". Cascading permissions would nullify that level of control.

Then again, Ghostery does much of that now, and maybe does it better. I should give cascading permissions a try, it really could come out better than than suspected.

If you mark domains as Untrusted, then that will still be respected even in cascade mode...