Code: Select all
Site .azcentral.com
Accept from .facebook.com .facebook.net
Deny INCLUSION(SCRIPT, OBJ, SUBDOC)Code: Select all
Site .azcentral.com
Accept from .facebook.com .facebook.net
Deny INCLUSION(SCRIPT, OBJ, SUBDOC)Code: Select all
Site .facebook.com .facebook.net
Accept from .azcentral.com
Deny INCLUSION(SCRIPT, OBJ, SUBDOC)Thanks! That makes sense. OK, I just tried this, but for some reason it works for facebook.com, but not for facebook.net. What I mean is when I load the page, facebook.com no longer shows in the Untrusted list, but facebook.net does.barbaz wrote:You just had it backwards
Code: Select all
Site .facebook.com .facebook.net
Accept from .azcentral.com .facebook.com .facebook.net
Deny INCLUSION(SCRIPT, OBJ, SUBDOC)Well, I already know how to do that. And I can easily automate a light switch. The purpose of my query is to see how to use ABE to create an exception. Based on the FAQ, this seems like a valid use, no?barbaz wrote:If you want to turn on a light, you need to flip the light switch.
If you want scripts from both facebook.com and facebook.net to run, you need to Temp-Allow both facebook.com and facebook.net in NoScript.
Ok, I just tried that and now it doesn't work for either facebook.com or facebook.net. Both remain in the untrusted list. Sigh.As for the ABE rule, try duplicating the Site line into the Accept line, like this:Code: Select all
Site .facebook.com .facebook.net Accept from .azcentral.com .facebook.com .facebook.net Deny INCLUSION(SCRIPT, OBJ, SUBDOC)
Screwing in a loose lightbulb is certainly a valid thing to do, but that alone is not enough for the light to turn on.ginahoy wrote:The purpose of my query is to see how to use ABE to create an exception. Based on the FAQ, this seems like a valid use, no?
(emphasis mine)ginahoy wrote:Ok, I just tried that and now it doesn't work for either facebook.com or facebook.net. Both remain in the untrusted list.
Huh? I may not be explaining myself very well. I'm simply asking if there's a way to create an exception in NS so that a script from an otherwise untrusted site will automatically be allowed to run on a given website. If ABE rules are not capable of doing this and there's no other way to accomplish this feature in NS, then fine... it would be useful to know that so I can move on. I don't understand ABE syntax and its capabilities, which is why I'm asking.barbaz wrote:getting the expected results seems not to be a problem there.
I lost track of this thread. A belated thanks for that clarification. Your comment plus the discussion Barbaz linked in his last comment... NOW I think I understand.Thrawn wrote:ABE rules do not make exceptions from regular script blocking. They are an added, independent layer of filtering.
OK, I think I understand... the Deny action on the *last* line restrict access from all sites not explicitly listed after the Accept action, right?However, you can effectively use them to make exceptions from script-blocking, simply by allowing the site(s) and then applying ABE rules to restrict access as desired.
Yes it would, but you're then restricting *all* requests. This would include top-level documents, so you wouldn't be able to access facebook by clicking a link on this forum.ginahoy wrote:I'm not sure I understand the purpose of "INCLUSION(SCRIPT, OBJ, SUBDOC)" after the Deny action. Wouldn't just "Deny" work?
Thanks Barbazbarbaz wrote:Yes it would, but you're then restricting *all* requests. This would include top-level documents, so you wouldn't be able to access facebook by clicking a link on this forum.
There should be a message logged in the Browser Console, though, whenever an ABE rule fires.ginahoy wrote:Apparently there's no way to directly tell if a script is blocked by ABE since it no longer shows up as Untrusted in the NS menu.