On Wed, 14 Mar 2018, Shawn H Corey wrote: > On Wed, 14 Mar 2018 07:03:55 -0400 (EDT) > "Robert P. J. Day" <rpjday [ at ] crashcourse [ dot ] ca> wrote: > > > On Wed, 14 Mar 2018, Stephen M. Webb wrote: > > > > > On 2018-03-14 05:22 AM, Robert P. J. Day wrote: > > > > > > > > obviously, it's not a big deal since both /usr/bin and /usr/sbin > > > > are part of the normal search path for even regular users, > > > > > > Only on an improperly configured system. /sbin and /usr/sbin should > > > not be in $PATH for a regular user. > > > > i disagree ... there are all sorts of utilities in /usr/sbin > > that regular users might find useful, and there can't be any > > security issues with that since users could always just add that > > to their PATH in their .bash_profile. > > Modern computers are either a PC, which has only one user that needs > to maintain the system, or a server, which should not be accessible > by regular users. even if you're that one user that needs to maintain the system, we all know the cardinal rule that you never log in as root, and that you should have a non-root account from which you can "sudo" as necessary. but there are all sorts of "admin" commands like "mount" that can be run as a regular user if you simply want to *display* information, and it would be a total pain if you had to keep using "sudo" just to list what was currently mounted. again, i see no problem in even regular users having /usr/sbin in their standard search path. rday