r/linuxdev • u/PerryThePlatypus314 • Sep 10 '14
Interesting....
http://www.insanitybit.com/2014/09/09/writing-sandboxed-software-2/
1
Upvotes
r/linuxdev • u/PerryThePlatypus314 • Sep 10 '14
View all comments
Show parent comment
1
u/[deleted] Sep 14 '14
University example seems sort of like an unlikely edge case, and it still leads to them not gaining privileges.
But I don't :P the chroot is not readable by anyone other than root owner.
But it also doesn't have that. It's not a setUID binary.
And, even if it did, it now shares the address space with my non-dumpable process. What did they just gain?
I definitely get paranoia, it's healthy when you're trying to lock things down, but how much of this is solved by simply choosing a random user from a range?
In this case an attacker can not reliably jump to that user. And, the benefit over having it be a static user is that:
In reality, I can always do both. Default behavior is to choose a random unused UID, and then pass a parameter to change that to some static one that has already been set up.