NoScript Security Suite de Giorgio Maone

4,4 stele din 5

1.723

292

168

121

107

Recenzie de către Utilizator Firefox 14275679

de Utilizator Firefox 14275679, 7 ani în urmă

UPDATE: It seems, although the Firefox add-ons page was reporting NoScript 10.1.9.4 it may not have been that version causing the issues, although Firefox had been re-started 3 times. Since writing the report (and those 3 re-starts after NoScript updated), the local page issues have now gone. Maybe 10.1.9.4 has to be run more than once for its fixes to the 10.1.9.2 bugs to take effect, and these are only picked up on browser re-start? The incorrect display of < noscript > has gone on the 4th re-start and the NoScript menu now shows a configurable file: domain for the first time since the major upgrade. Thank you for fixing! Changed from 1* to 3* [will be back to 5* if/when fully working].

FURTHER UPDATE: It has been working ok the rest of the day, so looks like the general incompatibility with Firefox 62.0 has also been fixed. Now back to 5* thanks.

ORIGINAL ISSUES [now fixed]:

As others have found, Firefox 62 plus the bad and admitted severe bugs in NoScript 10.1.9.2 have totalled its operation and the only way of using Firefox is to disable NoScript. Where do I start? All issues have been verified by disabling NoScript: without it no issues occur, with it enabled all occur, so it is the sole cause.

First, after a while, as others have reported, Firefox just stops working and will show nothing. From the console, it looks like NoScript has broken the Firefox origin policy on everything. Where is it trying to import scripts from?

The problem, reported on the NoScript forum that pages on local disks are broken since 10.1.9.2 on Firefox 61.0.2 remains. The scripts (used to) run but incorrectly also showed the content of < noscript >. A moderator proved this with a use case but the report has now been deleted. In Firefox 62.0, it is now worse. The page may load once (incorrectly) if you are lucky, then if you reload it stops (previous point). There is no facility in the current UI to specify permission for local pages (I think there was before the big change to the Firefox api)

Somewhere, probably in 10.1.9.2, the user list of allowed and blocked sites has been corrupted. 10.1.9.4 was supposed to fix this and recover the situation but hasn't [on the first or second runs].

As you just seem to delete some issues reported on your forums, please don't ask me to post there. Unless this barrage of severe errors is fixed quickly, the product is now unusable, sorry. I will be sad to have to uninstall it after around 5 years.

2.411 recenzii

Evaluat(ă) cu 5 din 5 stele
de Hopeavirta, 5 zile în urmă
Evaluat(ă) cu 5 din 5 stele
de Lazy Cat, 5 zile în urmă
Evaluat(ă) cu 5 din 5 stele
de sumobunny, 7 zile în urmă
Evaluat(ă) cu 5 din 5 stele
de Zelgadis-San, 7 zile în urmă
Evaluat(ă) cu 5 din 5 stele
de Dadou, 10 zile în urmă
Evaluat(ă) cu 3 din 5 stele
de aq, 12 zile în urmă
User 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
Evaluat(ă) cu 5 din 5 stele
de Simon Bünemann, 13 zile în urmă
Evaluat(ă) cu 5 din 5 stele
de ADKFZ8O, 18 zile în urmă
Evaluat(ă) cu 5 din 5 stele
de Marw, 21 de zile în urmă
Evaluat(ă) cu 1 din 5 stele
de aedgsegsfvw, o lună în urmă
WARNING! Causes crashes with SEVERE data loss. Since mid 2025, this extension regularly causes the browser to crash. It can even crash the browser so severely that windows freezes irreversibly, with SEVERE data loss as a result. The crashes stopped when I deleted this extension, and re-occurred after reinstalling it. Several others have reported the same issues on user forums.
Evaluat(ă) cu 2 din 5 stele
de Utilizator Firefox 15990777, o lună în urmă
Evaluat(ă) cu 1 din 5 stele
de Obs, o lună în urmă
It's not working.
Evaluat(ă) cu 5 din 5 stele
de Arman Daneshjoo, o lună în urmă
Evaluat(ă) cu 5 din 5 stele
de elmika, 2 luni în urmă
Evaluat(ă) cu 5 din 5 stele
de Utilizator Firefox 19469020, 2 luni în urmă
Evaluat(ă) cu 5 din 5 stele
de Utilizator Firefox 14500718, 2 luni în urmă
Evaluat(ă) cu 5 din 5 stele
de Utilizator Firefox 19459487, 2 luni în urmă
I'm notified every time WebGL is blocked on each page load. There's no way to disable these notifications and it's very irritating.

Edit: updated to 5 stars as it can be disabled after all but the setting isn't described very clearly.
Răspunsul dezvoltatorului
postat la 2 luni în urmă
You should not get any notification. Just a little placeholder inside the page, to be able to enable it back. And you can disable it by unchecking "NoScript Options>Appearance>Show synthetic placeholders for invisible capability probes"
Evaluat(ă) cu 5 din 5 stele
de Cello, 3 luni în urmă
it's 5-stars, because it's little time and effort to manage and also Edward Snowden said that noscript is the best protection in the whole internet...(after some Firefox update, noscript does seem to block internet in Firefox,,, but I'm sure there will be a workaround in the next edition ... buona vacanza)
Evaluat(ă) cu 1 din 5 stele
de Utilizator Firefox 19223232, 3 luni în urmă
ok its a good security 4 ur browser but now the web is so slow that i cant even play a game on poki 💀💀
Evaluat(ă) cu 5 din 5 stele
de Tony Klaus, 3 luni în urmă
Evaluat(ă) cu 5 din 5 stele
de Utilizator Firefox 19311874, 3 luni în urmă
Evaluat(ă) cu 2 din 5 stele
de Michael Rabinovsky, 3 luni în urmă
No Script is an incredibly useful add-on. In the past, I'd have given it five stars; it now gets only two (see issues below). All in all, I'd say it's still better to have it than not, but that's only because there is no better alternative, and there is no difference between having to completely disable it on a page versus not having it at all.

First of all, it would have gotten three due to the issues I list further down, but it gets two because of a major functionality problem that makes it obnoxious to use, and by its admission, not private in private windows.

In the past, when you set it to trust top-level domains, it would automatically set them to temp trusted; however, for whatever reason, it now sets them to "custom," for me, which functions the same as untrusted, and changing it doesn't even refresh the page for you.

The default setting handling is a huge inconvenience, but that is not where the problems end. You cannot restore previous functionality by manually setting the top-level domain to temp trust. To enable scripts on the page, you must set it to trust, which makes it permanently trusted, and keeps a log of every page you visit in private windows. If you try to change it to temp trust and refresh the page, it goes back to "custom."

Besides that, the description for the extension is outdated. Not only does it still mention Flash, but it also claims no loss of functionality when you need it, which is not true. In most cases, enabling some scripts will return the functionality you need, but there are several reasons why that's not always the case.

Sometimes, certain scripts you need will be on sub-domains of the top-level domain, and they need to be enabled separately; however, NoScript doesn't show them because it thinks they are part of the main domain, so you have no way to make the site work without completely disabling the addon for the page.

In other instances, sites won't load all the scripts until they load some other domains. For example, a CDN containing vital scripts might not appear on the list because it's called after an analytics script has run. There is no way to know that unless you enable each script on the list, one by one. The domain doesn't need to be related; it's just something about how the page loads.
Evaluat(ă) cu 1 din 5 stele
de Angel, 3 luni în urmă
Esta vaina debería tener un modo automático para aquellos que no saben de programación.
Evaluat(ă) cu 5 din 5 stele
de whatever, 3 luni în urmă
Evaluat(ă) cu 5 din 5 stele
de HunterMirror, 3 luni în urmă
He notado en las demás reseñas, que las personas no parecen comprender el propósito de este addon. La idea es que bloquee los scripts, si una página se rompe por ello, es algo perfectamente esperable, no es culpa de la extensión perse, sino de quien desarrolló dicha página web, queda a tu criterio si lo quieres añadir a la lista blanca o no. Lo realmente triste y reprochable, es más bien que hoy en día hayan tantas páginas que quieran que actives los scripts si o si para poder usarlos, incluso páginas que no los necesitan para nada.

El abuso de los scripts y la manía de convertir las páginas web en "aplicaciones", es lo que ha causado que ahora usar el navegador implique un consumo cada vez mayor de RAM, sin contar los riesgos de seguridad innecesarios del uso de scripts, tanto para el usuario como para el webmaster/desarrollador. Así que por mi parte, prefiero que se rompan las páginas que sean, no les voy a activar los scripts si no son páginas que hagan un uso inteligente y justo de ellas.

Răspunsul dezvoltatorului