Also, let me point you to the Legacy Browser Support extension.
https://chrome.google.com/webstore/detail/legacy-browser-sup...
With proper GPOs you can force a domain/subdomain to open in IE directly from any links.
Also, let me point you to the Legacy Browser Support extension.
https://chrome.google.com/webstore/detail/legacy-browser-sup...
With proper GPOs you can force a domain/subdomain to open in IE directly from any links.
Haven't used it for years but back when I was a Windows sysadmin it was the final proof that FF was better than IE: in addition to being Firefox it could also be IE : )
I would like to run 3-4 browsers at all times, each with totally sandboxed identity and IP address.
However I do not necessarily want to run a full blown VM for each of them.
This is very simple and efficient for sandboxing server daemons - I do it all the time and there is almost zero overhead involved in chroot/jail. However I have never chrooted a GUI application and cannot find any instances/recipes of anyone chrooting a browser ...
It appears that this does the things I am looking for - however, I am suspicious - why do we need a new project like this rather than a simple recipe for the existing jail or chroot system calls ?
What is it that makes something like firejail necessary ?