Just to point out, viewtopic.php?f=7&t=20723 , It does not sound like those entries were added by the user even accidentally.
So how useful is this safety catch if it's only in the Options dialog?
Is it realistic to implement it globally somehow?
RFE: Prevent whitelisting of http:
Re: RFE: Prevent whitelisting of http:
*Always* check the changelogs BEFORE updating that important software!
-
Re: RFE: Prevent whitelisting of http:
I expect that it is - just reject those entries when reading the whitelist - but the question remains, how did this happen? It shouldn't be possible for a webpage to trigger it, and what could have been in the browser that would insert NoScript whitelist entries?barbaz wrote:Is it realistic to implement it globally somehow?
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Fedora; Linux i686; rv:37.0) Gecko/20100101 Firefox/37.0
Re: RFE: Prevent whitelisting of http:
viewtopic.php?p=81264#p81264barbaz wrote:It does not sound like those entries were added by the user even accidentally.
*Always* check the changelogs BEFORE updating that important software!
-