4 ms·
Hadn't thought of it before but it might be an idea to run my browser (Firefox, Kubuntu 17.04) under a separate user that doesn't have access to my main user fi
by pbhjpbhj 9y ago
Hadn't thought of it before but it might be an idea to run my browser (Firefox, Kubuntu 17.04) under a separate user that doesn't have access to my main user files.
Might be simplest to just create a user through the DE, then "su -c" from my main user to run the browser?
- unkown-unknowns 9y agoOut of the box it'll probably tell you "Client is not authorized to connect to server" if you try to run anything X11 as another user. However it should be possible to configure your system such that it doesn't like such: https://wiki.archlinux.org/index.php/xorg#X_clients_started_with_.22su.22_fail https://wiki.archlinux.org/index.php/xorg#X_clients_started_...
- pbhjpbhj 9y agoI currently run my kids browsers under my user by doing "xhost +local:; su -l -c /usr/bin/firefox $USERNAME" where USERNAME is the kids login. I may have made changes to enable that, don't recall sorry.
- digi_owl 9y agoAn extra layer of protection may be offered by using the likes of xpra. https://xpra.org/ https://xpra.org/
- 482794793792894 9y agoUploading files would become a chore, as you'd always have to copy them over from your actual Home-directory to that Firefox-user's, but yeah, it would add another thick layer that attackers would have to get through. Mind that Firefox is also getting sandboxed tabs as we speak, so yet another layer that attackers would have to get through, which wasn't in place at the time of this attack.
- pbhjpbhj 9y agoCan make the user have read access to specified folders on the main user, seems easy enough.
- cesarb 9y agoAnother option would be a sandboxing system like xdg-app. AFAIK, there's already a xdg-app release of LibreOffice, and an experimental xdg-app build of Firefox. And, of course, there's always the paranoid option of "run the browser within a virtual machine", so an attacker would have to break the browser, then get local root within the VM, and finally find an exploit for the VM, before getting to your files.