On Tue, Jan 8, 2013 at 10:54 AM, Jean-Philippe Ouellet <jean-phili...@ouellet.biz> wrote: > Hello misc@, > > I'm researching locking things down, and I'm wondering what the current > best practice is for isolating risky programs. It seems this community > has traditionally shunned virtualization as a solution, and also called > exclusively chrooting "insufficient". Okay, sure. > > But what is better then? > > Say, for example, I'm running firefox, and I don't trust it. Running it > as-is straight out of pkg_add doesn't run it as its own user: > > $ ps -o user,command | grep firefox > jpouellet firefox > > As I understand it, the next time a remote code execution vulnerability > comes along, it could, among many many other things, read my > ~/.ssh/id_rsa and then it's game over.
Then don't use a private key without a pass phrase. Or run Firefox under a different user. Or run it in a jail. Or set up a VM on an isolated network and forward that X11 session back to your desktop. Or have a different system on your desk to use for web surfing and use a KVM switch. There are several solutions to the problem you've identified. Let me identify another: you're being way too paranoid. -Gene
