permanent allows for objects
permanent allows for objects
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.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:13.0a1) Gecko/20120201 Firefox/13.0a1
Re: permanent allows for objects
Are you referring to NoScript's whitelist?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.
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.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28
Thanks
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.
Code: Select all
Site ALL
Accept INC(OBJ,OBJSUB) from *.site.com
Deny INC(OBJ,OBJSUB)
Code: Select all
Site *.site.com
Accept INC(OBJ,OBJSUB)
Site ALL
Deny INC(OBJ,OBJSUB)
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:14.0) Gecko/20120420 Firefox/14.0a1
Re: Thanks
Because the syntax corresponds to the HTTP Request model, which may indeed seem backwards or counter-intuitive.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)
"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
Code: Select all
Site .google-syndication.com
Accept from .favesite1.com .favesite2.com .favesite3.com
Deny
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.

Last edited by Tom T. on Sat Apr 28, 2012 7:50 am, edited 1 time in total.
Reason: corrected foobar of "analytics" where "syndication" was meant. :-(
Reason: corrected foobar of "analytics" where "syndication" was meant. :-(
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28