NS Permissions Greyed Out

[GµårÐïåñ]

Ok Giorgio, done and sent. Let me know if you need anything else. 99% of the difference in the files was the crap left by extensions like WOT and couple others, the guts of the two were pretty much the same.

[Giorgio Maone]

In the OP screenshot, what causes the brackets [ ] to display?

It's displayed when JavaScript is disabled per-tab (usually by another extension, such as Tab Mix Plus).

[GµårÐïåñ]

You already know this but just for the record, I do not have TMP on my system. Gave it up a long time ago when it started causing more problems than the benefits it provided. Also, I don't have any other tool that disables JS or control it other than NS.

[Giorgio Maone]

You already know this but just for the record, I do not have TMP on my system. Gave it up a long time ago when it started causing more problems than the benefits it provided. Also, I don't have any other tool that disables JS or control it other than NS.

Problem is, NoScript in its default configuration (NoScript Options|Reset) never blocks JavaScript on per-tab basis.
Have you got any Sandbox ABE rule in your rulesets?
Also, did you try resetting the proxy config preference hijacked by abine as I suggested you by email?

[GµårÐïåñ]

Yes you are of course correct, by default it won't but as much as I love you, I don't use the default settings for NS so just put that out there. That's why I was careful to add that I configured the test profile install closely to how I had it in the other profile (minus the whitelisted items). And no, on this profile, NO ABE rules other than the default LOCAL that comes with it. My hardcore ABE rules are in the profiles where I do sensitive stuff, this profile is my daily use one, so nothing super fancy, just tightened up and secure but not overtly.

Anyway, back to the topic, yes, I got your email, did everything you suggested and wrote you back a fairly detailed list of stuff. Do you want me to post it here too?

Edit: Decided to go ahead and put it out here even though not sure if we have reached the end of it, but nothing secret about the communication, so will post them here. Some personal elements are sanitized.

> I sent the Diff file, Giorgio's response:

Does resetting

network.proxy.autoconfig_url

help?

> Just some relevant stuff not explicitly discussed. The item referred to is something Abine puts in there designed to "anonymize" google searches which I hadn't caught, it had slipped through the updates, my bad. Which contains this path:

abine://auto-conf.js

When enabled, contains:

Code: Select all

function FindProxyForURL(url,host){if(url.match(/^http:\/\/(?:(?!chatenabled\.|mail\.|checkout\.|sites\.|docs\.|picasaweb\.|notebook\.|spreadsheets\.|wave\.|voice\.)[^.]+\.)?google\.com(?!\/accounts|\/a\/UniversalLogin|\/calendar|\/reader|\/health|\/notebook|\/wave|\/ig|\/a\/|\/apps|\/webmasters|\/contacts|\/voice)/i)) return 'PROXY proxy.googlesharing.net:80; DIRECT'; else return 'DIRECT'}

When disabled, contains:

Code: Select all

function FindProxyForURL(url,host){return 'DIRECT';}

> I tested everything and responded with the following <personal language is removed>

Some interesting findings.

I reset it and then tried it in the same session and it didn't work, same result. So I decided to restart the browser in case it was still in memory and had the same issue.

HOWEVER, I checked the config and saw that it was back, so I smacked myself on the forehead like the idiot that I was and forgot that Abine would put it back obviously on restart.

So I decided to actually disable it within the addon and then checked and the setting was gone. Then once confirmed that the damn thing stayed gone, by restarting again and checking, I went back to Google and due to its whitelisted status, it worked as expected.

HOWEVER (I know when will it end right when you click on a link from the search results, it will get blocked and the result is something similar to those NS links that appear on some blocked sites (you know what I mean?) then you have to click on that link to get the actual page that would have been loaded directly going from Google to that page normally.

So not sure what's going on but the specific issue reported (specifically on Google) seems to be resolved, but I will have to keep an eye on other sites because I have seen it happen elsewhere too, just Google was the easiest for testing purposes. Will keep you posted.

Thank you again. <snip>

So this is out here in case it helps anyone, specially for following the issue and also to see if this was just a coincidence that Abine was involved because it was Google, or it happens elsewhere too, like it did in therube's case.

[Jorgo]

In my setup, this happens as well and the culprit is the Googlesharing add-on. This is unfortunate for a paranoid person like me, but there seems to be no easy way to resolve this conflict on the user's end (I've tried disabling all SSL option in Googlesharing to no avail).

[therube]

This, GoogleSharing is a special kind of anonymizing proxy service, designed for a very specific threat. It ultimately aims to provide a level of anonymity that will prevent Google from tracking your searches, movements, and what websites you visit. GoogleSharing is not a full proxy service designed to anonymize all your traffic, but rather something designed exclusively for your communication with Google. ?

AMO: GoogleSharing 0.22

[GµårÐïåñ]

But it still acts as any other proxy and behaves in the same manner causing the issues none the less, specific threat or not. Mechanism of implementation is causing the issue.