The problem is, no explanation of this was given by NoScript to assist users with using the completely new UI. For example, is accessible through HTTPS thus its lock defaults to green (there's no reason to access the site via HTTP) and any second-level subdomains are included (IE, *.). Additionally, what the lock defaults to is determined by whether or not the domain is accessed through HTTPS or not. In other words, if lock is red, the permissions apply to, but not. If the lock is red, it matches the domain regardless of HTTP or HTTPS with the caveat that it's limited to that exact domain. If the lock is green, the permissions only apply if the domain is accessed through HTTPS. I think this is how it works: The color of the lock determines whether or not the permissions only apply to to the domain when accessed via HTTP (Secure). Match HTTPS Only - This seems to be what's confusing people.Custom - Similar to Trusted, though you specify exactly what types of objects are allowed.Scripts for the domain are explicitly blocked, permanently. A larger, brighter clock means they'll be reset to Default after a browser restart. Note that when this active, you can control whether or not the permissions are permanent or temporary by clicking the clock on the right side of Trusted. Trusted - Scripts for that domain are allowed.Default - This is the default state, scripts for that domain are blocked.Let me post something that I found on the NoScript forums:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |