[Resolved] Privileged pages handling

[witrak()]

On some pages, it's impossible to change NoScript setting. An attempt leads to the message "This is a privileged page, whose permissions cannot be configured.", and nothing can be done - there's even no list of domains involved in script downloading. It happens on Mozilla pages, some bank pages (transaction systems), etc. Sometimes it happens on pages I know nothing about.
I would like to know what is done before such a message is assigned to a site/page. Is this site checked and I can assume it is safe? Is NoScript allowing javascript on such a page?
Today I observed strange behavior (in fact it is second such case, AFAIR): after the first attempt when the page in question hasn't opened I reloaded it after a couple of minutes and this time NoScript has shown the list of domains. So after some time, the site responded with new content, not privileged this time, I guess.
This suggests, that it is the current content of a page considered when the "privileged" status is assigned and displayed. Am I right? (BTW The URL in question is http://www.givemeit.com/)

[barbaz]

(BTW The URL in question is http://www.givemeit.com/)

That site seems down, neither I nor isitup.org are able to connect to it -

www.givemeit.com seems to be down!

Do you have another example?

[witrak()]

(BTW The URL in question is http://www.givemeit.com/)

That site seems down, neither I nor isitup.org are able to connect to it -

www.givemeit.com seems to be down!

Do you have another example?

Unfortunately, I don't have any example at hand what isn't strange because it is really rare situation.

Nevertheless, the reaction of NoScript is strange.
Still, I would like to know more about the meaning of the diagnostics displayed by NoScript...

[barbaz]

Still, I would like to know more about the meaning of the diagnostics displayed by NoScript...

If I'm understanding the relevant code correctly, NoScript shows that message when:
1) it can't obtain info on scripts for the page, and
2) the page is either listed in https://github.com/hackademix/noscript/ ... tricted.js or is not a http(s) page.

[witrak()]

As the second possibility seems to cover only Mozilla sites and in that case, the real reason is of secondary importance we have the problem of distinguishing pages where one can and should expect such diagnostics from others (where it can suggest the page isn't worth the risk of allowing scripts to run).
For such case the message is not appropriate, because it doesn't reveal (in implied form even) the information about the risk.

I would be more happy seeing two different messages, depending on these two cases - first of them clearly stating that NoScript is unable to block potentially dangerous scripts as analysis of the page is impossible.

[barbaz]

The conditions (1) and (2) I wrote are not two separate cases. They must BOTH be met for the "privileged page" message to appear.

[witrak()]

The conditions (1) and (2) I wrote are not two separate cases. They must BOTH be met for the "privileged page" message to appear.

Sorry, I didn't read your response carefully enough...

That resolves the matter.
Thank you!

[barbaz]

You're welcome