Análises para NoScript Security Suite
NoScript Security Suite por Giorgio Maone
Análise por Utilizador do Firefox 13446037
Avaliado em 3 de 5
por Utilizador do Firefox 13446037 , há 8 anos WebExtension is a big change, so former NoScript is dead and NoScript 10 is just a new extension.
Hopefully the developer will probably recover some advanced features of the XUL version, but it will take time we must be patient.
As today, there is no alternative on Firefox 57.
It seems that developer of the excellent ScriipSafe on Chrome Webstore doesn't want to port it on Firefox.
He could have done this for Microsoft Edge since a long time, and nothing has been done.
And surfing without a script controller is I M P O S S I B L E
.
I just don't understand why Mozilla team has not developed a basic embedded javascript manager as it was in the very good former Opera 16 (presto engine), so it could have let all the time to the third party developers to create a more advanced extension.
This is not acceptable, THIS IS A VERY BIG FAULT from Mozilla.
The main issue I could address now to the developer is :
1) no possibility to grant authorization to a full domain (this is a big difference with ScripSafe which lets the choice to the user)
Example : I want to authorize domain and all subdomain of the CDN provider Akamai, This si possible with scripsafe by using the "trust" option instead of "allow", it is not possible here
I want to authorize all Akamai because due to load balancing process the CDN server may change a lot, and so you still need to allow various subdomain. Maybe the developer could implement very quickly a joker system allowing to enter domains like :
*.akamai.net
*.hd.akamai.net
In first case we allow every subdomain of akamai.net
In the second case we limit to every subdomain of hd.akamai.net
2) No synchornization option
Ideally, NoScript should store the users data in cloud through the Firefox account as ScripSafe does in the Google Account.
But maybe it is not possible according to the Firefox account policy, so the workaround should be to be able to synchronize data to/from a local path on the computer.
One just have to create this path in a OneDrive or Google Drive synchronized directory...and this should be done.
I have several computer, each computer has several users session, this is just annoying to set up NosSript for each repeating always the same process. And when I set up a new computer, I must restart from the beginning.
With ScripSafe, this is very easy... the extension automatically download and upload to Google Accounts (one must activate such option).
If ScripSafe is ever ported to Firefox with the same functionalities, I drop NoScript
3) Slow GUI
As today, the NoScript GUI is I N C R E D I B L Y slow.
As a comparison ScripSafe is incredibly fast to display the distant hosts list
But this version is a kind of quick done dirty version, let's be patient, this will be probably fixed in the future, but developer must know that the situation is as today not acceptable. I also suspect that NoScript 10 slows down the browser
4) Inefficient filtering mechanism
In the former XUL extension, the filtering engine of NoScript was crappy as it was oftenly forgetting a lot of distant host.
So one needed sometimes to switch to "allow all scripts" to see these hosts, and go back to "forbide all scripts", and so we could set rules for theses invisible hosts.
As compared, ScripSafe was far better as there was not such issues.
Finally.... XUL NoScript is dead and this is a very good thing because the filtering engine of NoScript was outdated and the author didn't want to admit that.
Let's see now if this brand new Web Extension addresses such issues, I can't say at this moment.
Hopefully the developer will probably recover some advanced features of the XUL version, but it will take time we must be patient.
As today, there is no alternative on Firefox 57.
It seems that developer of the excellent ScriipSafe on Chrome Webstore doesn't want to port it on Firefox.
He could have done this for Microsoft Edge since a long time, and nothing has been done.
And surfing without a script controller is I M P O S S I B L E
.
I just don't understand why Mozilla team has not developed a basic embedded javascript manager as it was in the very good former Opera 16 (presto engine), so it could have let all the time to the third party developers to create a more advanced extension.
This is not acceptable, THIS IS A VERY BIG FAULT from Mozilla.
The main issue I could address now to the developer is :
1) no possibility to grant authorization to a full domain (this is a big difference with ScripSafe which lets the choice to the user)
Example : I want to authorize domain and all subdomain of the CDN provider Akamai, This si possible with scripsafe by using the "trust" option instead of "allow", it is not possible here
I want to authorize all Akamai because due to load balancing process the CDN server may change a lot, and so you still need to allow various subdomain. Maybe the developer could implement very quickly a joker system allowing to enter domains like :
*.akamai.net
*.hd.akamai.net
In first case we allow every subdomain of akamai.net
In the second case we limit to every subdomain of hd.akamai.net
2) No synchornization option
Ideally, NoScript should store the users data in cloud through the Firefox account as ScripSafe does in the Google Account.
But maybe it is not possible according to the Firefox account policy, so the workaround should be to be able to synchronize data to/from a local path on the computer.
One just have to create this path in a OneDrive or Google Drive synchronized directory...and this should be done.
I have several computer, each computer has several users session, this is just annoying to set up NosSript for each repeating always the same process. And when I set up a new computer, I must restart from the beginning.
With ScripSafe, this is very easy... the extension automatically download and upload to Google Accounts (one must activate such option).
If ScripSafe is ever ported to Firefox with the same functionalities, I drop NoScript
3) Slow GUI
As today, the NoScript GUI is I N C R E D I B L Y slow.
As a comparison ScripSafe is incredibly fast to display the distant hosts list
But this version is a kind of quick done dirty version, let's be patient, this will be probably fixed in the future, but developer must know that the situation is as today not acceptable. I also suspect that NoScript 10 slows down the browser
4) Inefficient filtering mechanism
In the former XUL extension, the filtering engine of NoScript was crappy as it was oftenly forgetting a lot of distant host.
So one needed sometimes to switch to "allow all scripts" to see these hosts, and go back to "forbide all scripts", and so we could set rules for theses invisible hosts.
As compared, ScripSafe was far better as there was not such issues.
Finally.... XUL NoScript is dead and this is a very good thing because the filtering engine of NoScript was outdated and the author didn't want to admit that.
Let's see now if this brand new Web Extension addresses such issues, I can't say at this moment.
2419 análises
- Avaliado em 4 de 5por Utilizador do Firefox 18127040 , há 4 diasТакие прям зайки и лапочки... Разместить закрытие окна приветствия и "Пожертвовать" чуть ли не с наложением друг на друга. Эдакое "Ну, даааааайти деняяяяяях!". Звезда в минус.
Аддон классный, но не нужно быть, как эти. - Avaliado em 5 de 5por Utilizador do Firefox 19664008 , há 14 dias
- Avaliado em 5 de 5por Utilizador do Firefox 19487299 , há 16 dias
- Avaliado em 5 de 5por Ryan Steed , há 25 dias
- Avaliado em 5 de 5por ZeroUnderscoreOu , há um mês
- Avaliado em 5 de 5por Bob , há 2 meses
- Avaliado em 1 de 5por mlatpren , há 2 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á 2 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á 2 meses
- Avaliado em 5 de 5por Lazy Cat , há 2 meses
- Avaliado em 5 de 5por sumobunny , há 2 meses
- Avaliado em 5 de 5por Zelgadis-San , há 2 meses
- Avaliado em 5 de 5por Dadou , há 2 meses
- Avaliado em 3 de 5por aq , há 2 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á 2 meses
- Avaliado em 5 de 5por ADKFZ8O , há 2 meses
- Avaliado em 5 de 5por Marw , há 3 meses
- Avaliado em 2 de 5por Utilizador do Firefox 15990777 , há 3 meses
- Avaliado em 5 de 5por Arman Daneshjoo , há 3 meses
- Avaliado em 5 de 5por elmika , há 4 meses
- Avaliado em 5 de 5por Utilizador do Firefox 19469020 , há 4 meses