4 ms·
We recently used them at work to easily implement role based access control to an internal REST service since unix sockets have the useful ability of being able
by seiferteric 5y ago
We recently used them at work to easily implement role based access control to an internal REST service since unix sockets have the useful ability of being able to tell which user is reading/writing to them. So you don't need to provide passwords or certificates because if the user is logged in on the system, they are already authorized.
- sethammons 5y agosu -u $otherUser Wouldn't that mess it up?
- seiferteric 5y agoYou need the other users password to do that, or be root, so it is not a problem. Also, in our system, non admin users don't have linux shell access anyway, they get a custom shell that uses the rest server as the backend. The admin user can get linux shell and run commands as other users or do whatever they want but that is expected.