Firefox Multi-Account Containers のレビュー
Firefox Multi-Account Containers 作成者: Mozilla Firefox
Amazing Mr. X によるレビュー
5 段階中 2 の評価
Amazing Mr. X によるレビュー (2年前)This 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.
合計レビュー数: 7,054
- 5 段階中 1 の評価Firefox ユーザー 18033912 によるレビュー (2日前)I've given up on this.
There are some great ideas, but the usability is abysmal, development has been basically non-existant for years.
- The extension constantly asks you which container to use even when its the first time you've gone to a website in a specific container or even when you specifically ask it to use a certain container.
- Its also incredibly annoying to try and use the same domain in two containers, in contrast to what the addon claims, because the extensions keeps panicking about which to open and tends to override your current container choice at will.
- Its impossible to migrate your addon config to another profile or device, only the container names can be backed up.
I've used it for years and have found it to be more trouble than its worth. Rather than having a simple all-in-one profile swapper it is more akin to just colored tabs that break websites, make it impossible to use the same domain in multiple containers without hassle and doesn't respect your explicit choice of container half the time. - 5 段階中 5 の評価nnldsnkd; s によるレビュー (3日前)
- 5 段階中 5 の評価Tucker によるレビュー (3日前)
- 5 段階中 5 の評価Firefox ユーザー 18464864 によるレビュー (4日前)This application is fantastic ! I recommend it to anyone who enjoys Firefox as much as I do <3
- 5 段階中 2 の評価Firefox ユーザー 12878065 によるレビュー (4日前)Great addon and idea, but the sync is a complete sh*t show. When deleting containers, they just somehow reappear, and if likely you'll end up with TWO, since it seems to restore the one you deleted and then pull one from the sync. In short, the Sync feature is completely useless, and have left me with at least 5 duplicates of every container I tried to delete. Can you PLEASE fix this? And there's no way to purge what's stored on the cloud.
- 5 段階中 5 の評価THEDZKO によるレビュー (5日前)Amazing feature! Allows a way more convenient way of managing different accounts from the same website and, at the same time, it is great that is an optional extra feature from the Mozilla Team. Recommended.
- 5 段階中 5 の評価Firefox ユーザー 13326192 によるレビュー (6日前)
- 5 段階中 5 の評価Firefox ユーザー 13666027 によるレビュー (6日前)Helps me to login to multiple aws account without opening private window or another browser
- 5 段階中 5 の評価Firefox ユーザー 16840430 によるレビュー (6日前)
- 5 段階中 5 の評価Firefox ユーザー 18460331 によるレビュー (7日前)
- 5 段階中 5 の評価dayfuaim によるレビュー (7日前)
- 5 段階中 5 の評価Firefox ユーザー 18458451 によるレビュー (8日前)Killer feature! The reason of my switch from other browsers.
- 5 段階中 5 の評価dobeerman によるレビュー (9日前)
- 5 段階中 5 の評価janlole によるレビュー (9日前)
- 5 段階中 3 の評価profile12 によるレビュー (10日前)
- 5 段階中 5 の評価CLXD によるレビュー (14日前)
- 5 段階中 5 の評価ka によるレビュー (14日前)
- 5 段階中 5 の評価Francio によるレビュー (16日前)
- 5 段階中 5 の評価Firefox ユーザー 17558216 によるレビュー (16日前)
- 5 段階中 5 の評価Firefox ユーザー 17579834 によるレビュー (16日前)
- 5 段階中 5 の評価mersun によるレビュー (16日前)
- 5 段階中 5 の評価Firefox ユーザー 18411001 によるレビュー (17日前)Linus tech tips would not have been "hacked" if he used this extension.