91–100 of 222 posts
I'm long searching for a solution to do this is a much broader way.. On the OS level. Private Work A Work B Work C Ideally it would seem like a different user. (Filesystem, cmd-tab). But easily accessible like the three finger swipe. Fast user switching doesn't cut it. I even tried logging in on my local machine using VNC or remove desktop.. Is having 4 VMs the only way?
I'm long searching for a solution to do this is a much broader way.. On the OS level. Private Work A Work B Work C Ideally it would seem like a different user. (Filesystem, cmd-tab). But easily accessible like the three finger swipe. Fast user switching doesn't cut it. I even tried logging in on my local machine using VNC or remove desktop.. Is having 4 VMs the only way?
Earlier quoted context omitted.
Just run "firefox --no-remote -ProfileManager" and here you go. I'm sure Grandma and Joe SixPack will do that... Not everybody is tech savvy. I'd say the majority of FF users don't even know there's a profile manager.
Reminder of the thing it's being compared to: > The containers feature is enabled in Firefox Nightly 50 by default with the about:config pref `privacy.userContext.enabled` set to true. Grandma and Joe SixPack aren't running Firefox Nightly with about:config tweaks either.
Example: my main general browsing profile has flash, PDFs and all plugins disabled, absolutely all handlers switched off, all hardware access off, WebGL switched off, no account logins and uBlock Origin set to aggressively block most third-party requests.
My second most used context is for personal sites I login for - with access to third-party cookies (for those sites) and running most third-party requests with standard uBlock rules.
I have yet other contexts (Chrome profiles) where Flash is enabled if I need that, then a separate browser for Java etc.
I'd like to see these security levels built into browsers where the contexts are built around permissions and site trust rather than access to the user store (which is also important)
I don't think it's realistic for most users to do this right now with profiles, as it requires a lot of discipline - it needs to be in the UI.
Browsers have become as sophisticated as operating systems and we're accessing more and more of our personal data using them, yet the model of 'every site has access to everything' be it a site you trust, like Gmail, or a random URL you're clicking on - has somehow survived.
It's the equivalent of the old days where everyone would run their local systems with an admin account for everything. I really think browsers need a rethink along these lines where websites are treated like apps and you can apply a trust group to each.
I'm long searching for a solution to do this is a much broader way.. On the OS level. Private Work A Work B Work C Ideally it would seem like a different user. (Filesystem, cmd-tab). But easily accessible like the three finger swipe. Fast user switching doesn't cut it. I even tried logging in on my local machine using VNC or remove desktop.. Is having 4 VMs the only way?
Long time ago (win2000, before XP)I tried to do it on windows with the "runas" command, but things like IE would keep popping up with the wrong user (they managed to communicate with the desktop and have that open the new window) so it wasn't a good solution. Perhaps it is better now.
Right now, what I'm doing is that all my standard browsing happens on Firefox, with uMatrix blocking JS and just generally locked down. For anything where I want to log in or have a persistent identity (stackoverflow, gmail, etc), I set up separate Chrome profiles and manually open each site in the appropriate profile. Honestly, this whole thing is a bit of a pain - my ideal solution would be one where I can set up "…
FWIW, this is also doable in Firefox: try 'firefox --new-instance -ProfileManager'; you can also directly open up a new profile from the command line (and hence do the same from scripts, desktop entries, or whatever else your platform supports).
I have one profile for my finances, one with NoScript in blacklist mode, and then my normal profile.
I would like to be able to configure my browser to open every URL in a domain-specific "container", unless I say otherwise. Say site www.a.org includes an image from www.evilcorp.org, and www.evilcorp.org sets a cookie. When I then go to www.b.org and it includes an image from www.evilcorp.org, I don't expect the cookie to be sent back. In other words, the cookie should be tied to www.a.org, even though it actually c…
Earlier quoted context omitted.
Yes it does and I have been using this. But it seems to be per window not tab. Unless I've missed something?
> it seems to be per window not tab Chromium-based Ghost Browser [1] can do it per tab or tab group. It would be nice if Google implemented the same feature into Chrome since multiple profiles can be a hassle. [1] https://ghostbrowser.com
I've been doing this for years using both Firefox' and Thunderbird's multiple-profile features. Just run "firefox --no-remote -ProfileManager" and here you go. So the serious question is: how is this any different from using multiple profile? Multiple profile also have the pro/con that they are actual different processes, so there's no information leak between profiles whatsoever (well, unless some serious hacking ha…
It means you only have to do customization once. And you don't have to juggle multiple windows. It has a lower bar of entry.
I use separate Firefox profiles in order to have different add-on configurations, e.g. in my daily driver NoScript is set to whitelist mode, while in my special JavaScript-permitted profile it's in blacklist mode.
This is a neat idea but it doesn't implement the main reason I use separate profiles in Chromium - different security contexts based on how much you trust a site. Example: my main general browsing profile has flash, PDFs and all plugins disabled, absolutely all handlers switched off, all hardware access off, WebGL switched off, no account logins and uBlock Origin set to aggressively block most third-party requests. M…
This feature is not meant to solve that use-case since if your case is security, you need separate browsers/contexts/proceses anyways.
Separate profiles in firefox implement separate profiles (which may all be independently open side-by-side in different windows).
This exchanges less secure/strong separation with better UX by intermingling.
Firefox is just choosing to support either set of tradeoffs there.