InformAction Forums

there already are temporal allows for objects like java. maybe there should be permanent allows for them too. iv tried write java-vm@site.com for site, but it doesn't allow to do so.

finaryman wrote:there already are temporal allows for objects like java. maybe there should be permanent allows for them too. iv tried write java-vm@site.com for site, but it doesn't allow to do so.

Are you referring to NoScript's whitelist?

Try writing that rule in ABE. See ABE FAQ.

However, you would have to uncheck "Forbid Java" in NS Embeddings tab. ABE can only tighten NS's permissions; it can't loosen them.
So you allow all Java in NS, but then specify in your ABE rule which sites are actually allowed, and the rest are denied.

Sorry that your post fell through the cracks; apologies for the delay in responding.

for some reason this didn't work, could you tell me why? but i got it working by writing this. so, thanks for your help.

finaryman wrote:for some reason this didn't work, could you tell me why?

Code: Select all

Site ALL
Accept INC(OBJ,OBJSUB) from *.site.com
Deny INC(OBJ,OBJSUB)

Because the syntax corresponds to the HTTP Request model, which may indeed seem backwards or counter-intuitive.

"Site" is the source of the script (or whatever) that you wish to control.
"Accept from" is the site at which you wish to ALLOW (or deny) the source described in the first line.

It's easy to think that "Accept from" means the source of the blockable content. Like this:
Site favesite.com
Accept from google-syndication.com. = I think I'm telling favesite to accept content from google-syndication.

But this is not so.
In fact, what happens is this:

Your browser, upon landing at site.com, sees in the code that script should be called from, say, google-syndication.com. (advertising script)
So it *makes a request* to google-syndication, asking GS to send the script for execution.

NoScript checks to see whether you wish to allow site.com to make this HTTP request FROM site.com TO google-syndication.com.
If so, the request is made, and GS sends the script for execution.
If not, the request TO g-s.com is blocked. Or in other words, G-S is not allowed to accept requests from site.com
In this rule, I want to support my favorite sites by allowing them to request the G-S script, whereupon my fave sites will execute the GS script, run the ads, and get the money for so doing.
Or, more clearly, by *allowing G-S to accept requests from favesite.com".
All other sites will not be allowed to make requests to G-S. Or, in our model, G-S will not be allowed to accept requests FROM any other site.

I know it sounds backwards, but does this now make sense?

Advanced users will find more specific information than the FAQ in the ABE Rules .pdf, including the exact syntax for all of these.

And you're very welcome.