4 ms·
Yes, but you are effectively turning your box into a single user system. And that's fine if you are happy to work that way, but the origins of the directory str
by digitalsankhara 4y ago
Yes, but you are effectively turning your box into a single user system. And that's fine if you are happy to work that way, but the origins of the directory structure is of course in multiuser UNIX. As a sysadmin, I would not want my /bin /sbin exposed to everyone. In your example I question the security implications of being able to run those binaries outside of root anyway (esp. in a professional environment) if you have your box exposed on a network.
- Athas 4y ago> As a sysadmin, I would not want my /bin /sbin exposed to everyone. Why not? It's not like most of them are suid (right?). Most Unix systems I've used allow any user to peruse /sbin at their leisure and run whatever they want.
- digitalsankhara 4y agoApologies if I'm missing your point, but yikes - any user on your system can run /sbin/shutdown?
- Athas 4y agoYes of course, just like on more or less any Linux system. But IIRC, shutdown is a suid binary that will do its own permission checks while running. The permissions on the /sbin/ directory should not matter.
- mekster 4y agoDo you realize /bin is a symlink to /usr/bin these days?