NS Permissions Greyed Out

[GµårÐïåñ]

I have noticed today that when I tried to "allow/trust" a site, I find the option greyed out. Now before you all say, do you have HTTPS only enabled, NO. This is normal config and should NOT be greying out squat. So this is abnormal and wrong. Here is a screenshot:



I have only seen this happen when you access a regular HTTP site using the HTTPS option of (ALWAYS) and since that's not the configuration, why is this happening? Additionally, this is a fresh profile, clean install because the stupid 8.x update totally blew up all my profiles and I had to start over, so its completely clean. Ideas? Griogio?

If you care, here is the bug file on that: https://bugzilla.mozilla.org/show_bug.cgi?id=702489

[Giorgio Maone]

Did you try NoScript Options|Reset?
Also, does it happen on https://secure.informaction.com/ipecho ?

[GµårÐïåñ]

To add more insanity to this problem, I decided to change the HTTPS setting to something other than NEVER and see what happens and the result was even more inconsistent and bizarre. Changed it to (only when you use a proxy like tor) and then I get this which still makes ABSOLUTELY no sense. Its practically contradictory, specially since I don't use a proxy right now or on this machine.



Using general terminology, I think we we got a logic block/select block, that is not condition checking properly and is going to a part of the code that is not relevant to what is actually set to be. Otherwise, setting it to proxy wouldn't given you such a contradictory result and leaving it without anything giving us ALWAYS condition.

I think something got tweaked or broken in the latest round of code changes, hope this added information helps a bit.

[GµårÐïåñ]

Did you try NoScript Options|Reset?
Also, does it happen on https://secure.informaction.com/ipecho ?

No I didn't because as I said, this was a freshly created profile, it shouldn't have a reason to be broken and need to be reset. But if you insist its necessary, I will do it. But I don't see how a freshly created profile, whose had ONE ns install (no update) to this version, with only this being third time its being used would have an issue already.

With your link it gives this view with a white S and in both NEVER and PROXY mode of HTTPS, it gives this:



Anything else you want me to try? This is without reset by the way. After posting this, I will do a reset which should not be needed but anything to figure out what gives. I will post IF there is something different, which I don't expect will be but we'll see.

[Giorgio Maone]

May I see the complete list of the extensions enabled in that profile?

[GµårÐïåñ]

Giorgio, something else I noticed when I was trying to reset and it makes not sense either, unless my understanding of it is off, which after all these years would be tragic. You have a bunch of items on the mandatory list which show up light grey on the whitelist. Among is all the about:x stuff including about:blank and the wildcard about: which would match ANY about stuff, like the 192.168. would match any LAN IP. So explain to me why on a blank tab, about:blank is NOT allowed and shows up available? Given the whitelist setup, it should be allowed, no? I figured I won't waste time with screenshots but if you need to see what I mean, I can provide it. Something change?

[Giorgio Maone]

"about:" is not a wildcard but a full URL, in the about: protocol.

[GµårÐïåñ]

May I see the complete list of the extensions enabled in that profile?

Certainly, here you go (as seen on my screen)

[GµårÐïåñ]

"about:" is not a wildcard but a full URL, in the about: protocol.

Gotcha, I figured it was just a partial that would work the same as the local IP partials to avoid whitelisting them individually to account for any future about page being added, thanks for the explanation. However, it still doesn't explain why the about:blank on the list explicitly there doesn't get taken into account and makes it show up as available and untrusted by default on the menu?

[Giorgio Maone]

What if you disable them all except NoScript?

[GµårÐïåñ]

What if you disable them all except NoScript?

I'll do one better, give me a few minutes, I will create a whole new profile, with just NS and let you know. Bear with me.

[GµårÐïåñ]

Sorry took a bit longer, decided to do a bit more extensive series of stuff so I can give you a more rounded response.

1. Clean profile with just NS configured similar to the other profile (minus the items on the whitelist that are in the other profile) and it worked fine and seemed to do as expected.

2. In the profile in question, I reset with the extensions as-is and it came back to the same issue, even with Google ON the whitelist already it did the same thing as reported earlier.

3. In the same profile in question, I disabled all other extensions and came back to find the problem still exists as reported.

I have not actually done a prefs.js comparison between #1 and #3 to see why it would be different given that for all intents and purposes each profile only has NS active, but it has just added to the confusion which I was hoping it would resolve. Ideas? Anything you want me to do further?

[Giorgio Maone]

I have not actually done a prefs.js comparison between #1 and #3 to see why it would be different given that for all intents and purposes each profile only has NS active, but it has just added to the confusion which I was hoping it would resolve. Ideas? Anything you want me to do further?

diff $PROFILE1/prefs.js $PROFILE2/prefs.js

[GµårÐïåñ]

diff $PROFILE1/prefs.js $PROFILE2/prefs.js

Ok, I take that as you wanting me to do it, one thing I hadn't done yet. Off to go do that, give me a few and I will email you results to avoid having to sanitize it.

[therube]

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

Is HTTPS Always working?

If I set it to Always, I generated this from an already opened window (did not refresh or anything like that). Happens on some windows & not others. Others look normal.



Oh, that was weird.

Always enabled. Loaded tinypic.com. Allowed tinypic.com. AFAICT, https was not coming into play, site loaded far too fast for that. I selected the shot (above) to upload, & then realized that tinypic.com was NOT allowed (even though I had Allowed it, & seemingly it worked), & at that point the domains were grayed out.

Disabled Always, refreshed the page, then was able to Allow, then the upload actually uploaded.

2.2.2rc4
Aurora, Mozilla/5.0 (Windows NT 5.1; rv:10.0a2) Gecko/20111128 Firefox/10.0a2 SeaMonkey/2.7a2