Análises para Firefox Multi-Account Containers
Firefox Multi-Account Containers por Mozilla Firefox
Análise por Amazing Mr. X
Avaliado em 2 de 5
por Amazing Mr. X, a há 2 anosThis has a lot of potential, but it's not quite ready for prime time. There's a few specific problems here:
Firstly, add-ons can't communicate with the content of containers. This breaks functionality in most add-ons in really weird and unexpected ways. It'd be nice if we could whitelist add-ons to have access to relevant containers, but most users would probably want all of their add-ons to have full access to all of their containers by default and wouldn't expect them to be functionally blocked as they are.
Secondly, containers don't nicely handle redirects. A lot of sites, especially corporate ones, will redirect through several different domains and subdomains when performing the login process. Containers set to "Limit to Designated Sites" won't operate correctly with these redirects as the redirect pages are not true web pages and don't allow you to sit on them long enough to click the address bar button to always open them in the specified container. This cannot currently be remedied by having foreknowledge of the complete list of redirect sites, as the "Limit to Designated Sites" list cannot be manually edited or appended outside of the limited address bar button method.
Thirdly, The VPN integration isn't particularly secure in premise. Being a per-container opt-in means that entities snooping on the line will immediately see that there's something suspiciously different in the data packets coming from your protected containers compared to the rest of your typical https encrypted traffic. This makes isolating these packets, on the fly, infuriatingly trivial. Making this a per-container opt-out would all but eliminate this problem, as attackers would have to have foreknowledge of the originating container to do this effectively in all circumstances. It'd also be great to see connection protocol options ( OpenVPN, WireGuard, etc. ) as well as other VPN provider options as that'd make it that much harder to try and figure out what's going on in the encrypted container traffic and would better protect Mozilla VPN itself. Right now it's technically more secure to not use the VPN feature at all.
I think the basic idea here is really excellent, but these problems really do drag it down. Something made and maintained by Mozilla shouldn't have this many problems. I still think this is potentially useful to certain technical professionals trying to isolate their sensitive internal sites from other web apps, but the average user is going to have too many headaches to be able to use this effectively.
If you know what you're doing, keep the above points in-mind and go ahead and give it a try.
Anyone else? Hope Mozilla addresses some of these issues in a future release. I'll update my review if they do.
Firstly, add-ons can't communicate with the content of containers. This breaks functionality in most add-ons in really weird and unexpected ways. It'd be nice if we could whitelist add-ons to have access to relevant containers, but most users would probably want all of their add-ons to have full access to all of their containers by default and wouldn't expect them to be functionally blocked as they are.
Secondly, containers don't nicely handle redirects. A lot of sites, especially corporate ones, will redirect through several different domains and subdomains when performing the login process. Containers set to "Limit to Designated Sites" won't operate correctly with these redirects as the redirect pages are not true web pages and don't allow you to sit on them long enough to click the address bar button to always open them in the specified container. This cannot currently be remedied by having foreknowledge of the complete list of redirect sites, as the "Limit to Designated Sites" list cannot be manually edited or appended outside of the limited address bar button method.
Thirdly, The VPN integration isn't particularly secure in premise. Being a per-container opt-in means that entities snooping on the line will immediately see that there's something suspiciously different in the data packets coming from your protected containers compared to the rest of your typical https encrypted traffic. This makes isolating these packets, on the fly, infuriatingly trivial. Making this a per-container opt-out would all but eliminate this problem, as attackers would have to have foreknowledge of the originating container to do this effectively in all circumstances. It'd also be great to see connection protocol options ( OpenVPN, WireGuard, etc. ) as well as other VPN provider options as that'd make it that much harder to try and figure out what's going on in the encrypted container traffic and would better protect Mozilla VPN itself. Right now it's technically more secure to not use the VPN feature at all.
I think the basic idea here is really excellent, but these problems really do drag it down. Something made and maintained by Mozilla shouldn't have this many problems. I still think this is potentially useful to certain technical professionals trying to isolate their sensitive internal sites from other web apps, but the average user is going to have too many headaches to be able to use this effectively.
If you know what you're doing, keep the above points in-mind and go ahead and give it a try.
Anyone else? Hope Mozilla addresses some of these issues in a future release. I'll update my review if they do.
7018 análises
- Avaliado em 5 de 5por Utilizador do Firefox 16493129, a há 12 horasCannot do without this extension. Amazing tool!
- Avaliado em 5 de 5por nyanbinary, a há 17 horas
- Avaliado em 5 de 5por Utilizador do Firefox 18427376, a há 2 dias
- Avaliado em 5 de 5por Utilizador do Firefox 16977240, a há 2 dias
- Avaliado em 4 de 5por Utilizador do Firefox 18327230, a há 2 diasWould like to have the ability to switch between tabs opened in each container (especially with a keyboard shortcut), would also be great to use as the foundation for tab grouping for open bookmarks.
Let me know if either of these exist if I'm missing them! - Avaliado em 3 de 5por robisodd, a há 3 diasPlease, please, PLEASE! Allow an option to set the default action (in the URL bar) to "open this site as [container]" and not "ALWAYS open this site as [container]"! I cannot use this extension without this option (I am aware it is available buried in submenus of the separate extension icon). It doesn't need to be the default, just an option. I have spent HOURS removing hundreds of websites from the default "ALWAYS open" setting; not to mention the dozens of billable hours fixing users' issues with this setting.
- Avaliado em 5 de 5por Grimm, a há 5 dias
- Avaliado em 5 de 5por Utilizador do Firefox 17037715, a há 6 dias
- Avaliado em 5 de 5por Utilizador do Firefox 16880180, a há 6 dias
- Avaliado em 5 de 5por FrugalBard499, a há 7 dias
- Avaliado em 1 de 5por uberprutser, a há 8 diasI really like the idea of this extension, but its a lot of frustration for me. Container setup are not synced properly between devices, and when syncing with a Dutch computer I got all Dutch default containers mixed with my setup. After removing the extension, it just doesn't get removed completely. Rather frustrating!
- Avaliado em 5 de 5por Aleksey, a há 8 diasThe best tab management. Nothing on any browser stands even close.
- Avaliado em 5 de 5por TacoTrucks, a há 8 dias
- Avaliado em 5 de 5por Peter J., a há 9 dias
- Avaliado em 5 de 5por Utilizador do Firefox 18413408, a há 9 diasTellement facile d'isoler les sites trop regardants.
- Avaliado em 5 de 5por Utilizador do Firefox 18199950, a há 10 diasWorks great, super useful. Only thing missing is switching places for the option "Open in new container tab" from tab menu and button "Always open this in a Container" from address bar. The former is used more frequently, yet it requires clicking on tab menu and localizing the command. The latter could go to tab menu, it's rarely used.
- Avaliado em 5 de 5por AleCornella, a há 10 dias
- Avaliado em 4 de 5por dikunav, a há 10 dias
- Avaliado em 4 de 5por Laskoni, a há 11 diasIl y a des problèmes de connexion lorsqu'on connecte 2 comptes (gmail, par ex.) dans deux containers différents, c'est assez laborieux et ne fonctionne pas toujours.
- Avaliado em 5 de 5por Gin, a há 11 dias
- Avaliado em 5 de 5por Utilizador do Firefox 18409936, a há 12 diasVery useful add on for separating tabs by categories.
- Avaliado em 5 de 5por Utilizador do Firefox 17961461, a há 13 dias
- Avaliado em 5 de 5por Uthman, a há 14 dias
- Avaliado em 5 de 5por Utilizador do Firefox 12912935, a há 14 dias
- Avaliado em 5 de 5por Utilizador do Firefox 17668164, a há 16 dias