3 ms·
I don't have a problem running my test code on boxes with hostile people logged in to them, nor do my socket connections offer them anything they couldn't alrea
by jerf 5y ago
I don't have a problem running my test code on boxes with hostile people logged in to them, nor do my socket connections offer them anything they couldn't already do if they have that level of access. You sound like you may have a very particular problem, and if this is your situation I'm not convinced "Unix sockets" are the answer anyhow... you seem to have bigger problems with unauthorized access.
- kortilla 5y agoIsolation on a machine is a very basic security primitive. Binding to localhost circumvents all of that and you end up with vulnerabilities like this: http://benmmurphy.github.com/blog/2015/06/09/redis-hot-patch http://benmmurphy.github.com/blog/2015/06/09/redis-hot-patch Remember, anything you put on localhost can be reached by your browser (unless you use iptables with the pid owner check) and arbitrary webpages you are on can hit those endpoints in the background. The solution you are offering is worse both from a security and a usability standpoint.
- nerdponx 5y agoFYI- that link returns 404. "There isn't a GitHub Pages site here."