Análises para NoScript Security Suite
NoScript Security Suite por Giorgio Maone
Análise por Utilizador do Firefox 13551289
Avaliado em 2 de 5
por Utilizador do Firefox 13551289 , há 8 anos Ok, I just got the update and have to say I really hate the new version and am considering dumping it completely. There are a lot of reasons why.
Under the old version, when you visit a new website, it shows a popup saying that scripts are disabled and giving you a quick option to temporarily or permanently enable scripts for just that website. Under the new version, you don't even know if the scripts are blocked, and if the website is malfunctioning because it needs its scripts, or what.
Also, the new UI really sucks. Everything is all icons now and I don't have a clue what any of them do. Am I allowing scripts or blocking them? Am I permanently allowing them or just temporarily? You could at least give us the option to go back to the classic interface.
I've also noticed that for every single website I go to, I have to tell it not to allow XSS from that website to facebook.com. It's really annoying. There is no option to just say, don't allow XSS from anywhere to facebook.com. Under the old version, it only gave me an XSS warning for a certain few websites which I could then do an unsafe reload. Now it's like there's cross-scripts everywhere.
Ok so maybe a useful feature would be to allow for example facebook.com (seems to be the main offender here) when I'm ON facebook.com, but disable it when any other website tries to cross-script to it.
Anyway to sum it up, the new version nags me incessantly and isn't clear enough about what's going on for me to figure out how to allow the scripts I want and block the ones I don't. Please go back to the old version.
Under the old version, when you visit a new website, it shows a popup saying that scripts are disabled and giving you a quick option to temporarily or permanently enable scripts for just that website. Under the new version, you don't even know if the scripts are blocked, and if the website is malfunctioning because it needs its scripts, or what.
Also, the new UI really sucks. Everything is all icons now and I don't have a clue what any of them do. Am I allowing scripts or blocking them? Am I permanently allowing them or just temporarily? You could at least give us the option to go back to the classic interface.
I've also noticed that for every single website I go to, I have to tell it not to allow XSS from that website to facebook.com. It's really annoying. There is no option to just say, don't allow XSS from anywhere to facebook.com. Under the old version, it only gave me an XSS warning for a certain few websites which I could then do an unsafe reload. Now it's like there's cross-scripts everywhere.
Ok so maybe a useful feature would be to allow for example facebook.com (seems to be the main offender here) when I'm ON facebook.com, but disable it when any other website tries to cross-script to it.
Anyway to sum it up, the new version nags me incessantly and isn't clear enough about what's going on for me to figure out how to allow the scripts I want and block the ones I don't. Please go back to the old version.
Resposta do programador
publicado a há 8 anos1) The UI shows you all the domains that are trying to run active content, just like before, but more compact. You can allow them individually (by assigning the TRUSTED preset), leave them not running (DEFAULT), blacklisting (UNTRUSTED) or even assign CUSTOM permissions. Not just that, but better than before if you can modify each preset on the fly and even see the minimum permissions needed for the site to work (they've got a pink background).
2) To assign the TRUSTED preset temporarily, you just click it once. To make it permanent, you click the clock icon and make it fade away (temporary->permanent).
3) The XSS filter now has a "Always block requests from a.com to b.com" option, that you can use exactly the way you say you want.
2) To assign the TRUSTED preset temporarily, you just click it once. To make it permanent, you click the clock icon and make it fade away (temporary->permanent).
3) The XSS filter now has a "Always block requests from a.com to b.com" option, that you can use exactly the way you say you want.
2422 análises
- Avaliado em 3 de 5por Utilizador do Firefox 14609268 , há 16 horasWhile this is an incredibly great app for granular control, it is the OPPOSITE of its "with no loss of functionality" mission. This is the #1 go-to source of browser errors that I am constantly troubleshooting and it takes HOURS of time sifting to figure out what to tweak because it provides no help when it breaks something (like a search box)--you just have to go on a lengthy trial and error quest one by one to figure out which of 30 sites to trust to get a search bar working and by that time I don't remember what I was going to search for. So you end up just globally trusting everything and that defeats the whole purpose.
- Avaliado em 2 de 5por Utilizador do Firefox 13935566 , há 10 dias
- Avaliado em 5 de 5por Pompan , há 12 dias
- Avaliado em 4 de 5por Maximilien Perron , há um mês
- Avaliado em 4 de 5por Utilizador do Firefox 18127040 , há um mêsТакие прям зайки и лапочки... Разместить закрытие окна приветствия и "Пожертвовать" чуть ли не с наложением друг на друга. Эдакое "Ну, даааааайти деняяяяяях!". Звезда в минус.
Аддон классный, но не нужно быть, как эти. - Avaliado em 5 de 5por Utilizador do Firefox 19664008 , há 2 meses
- Avaliado em 5 de 5por Utilizador do Firefox 19487299 , há 2 meses
- Avaliado em 5 de 5por Ryan Steed , há 2 meses
- Avaliado em 5 de 5por ZeroUnderscoreOu , há 2 meses
- Avaliado em 5 de 5por Dzluck , há 2 meses
- Avaliado em 5 de 5por Bob , há 3 meses
- Avaliado em 1 de 5por mlatpren , há 3 mesesIt does a great job at blocking, but is regularly frustrating with re-enabling things. It's supposed to show you what it's blocking, but that's extremely hit-or-miss. Occasionally, there'd be something blocked where the only solution is to disable the extension. As in, right-click and disable *from Firefox itself.*
- Avaliado em 3 de 5por zekromVale , há 3 mesesThere needs to be a CPU limit on this extension, using 30% CPU of an intel i7 11th gen laptop CPU on YouTube is ridiculous. Firefox for Ubuntu snap, flatpack, or just .deb are affected. Must disable NoScript to fix it or allow everything fully for all domains on the page. I would like more domains to be added to the global trusted list though (by default) or have a popup at the top when you first visit a page.
- Avaliado em 5 de 5por Hopeavirta , há 3 meses
- Avaliado em 5 de 5por Lazy Cat , há 3 meses
- Avaliado em 5 de 5por sumobunny , há 3 meses
- Avaliado em 5 de 5por Zelgadis-San , há 3 meses
- Avaliado em 5 de 5por Dadou , há 3 meses
- Avaliado em 3 de 5por aq , há 3 mesesUser for at least 15 years, Something is conflicting on Firefox. It is blocking scripts and other add ons such as tampermonkey or violentmonkey with scripts added, but without any listing of what is being blocked. Only option is to shut it off to proceed.
Even blocking games internal scripts without any 'monkey' in use.
Please check and test - Avaliado em 5 de 5por Simon Bünemann , há 3 meses
- Avaliado em 5 de 5por ADKFZ8O , há 4 meses
- Avaliado em 5 de 5por Marw , há 4 meses