Quoting Tom Rauschenbach <[EMAIL PROTECTED]>:
> I;m hearing that root access is seldom if ever needed.  I'm hearing talk of
> production environments, engineering environments, development envronments
> etc.  Let's talk about "my machine".  Not my workstation at work, not a
> machine
> somebody else owns, not my wife's machine not nothing.  MY PC running
> LINUX.
> Should I use root login or sudo ?  Simple question.  

  In a home environment, I personally just use root, and don't worry about 
sudo.  Now, I have other *users* that use my home machine, and they have the 
ability to mount and unmount remote drives (I have a small 486 just serving as 
a File server).  THEY do so via sudo.

> Hard question.  Is the answer to the simple question (whatever the answer
> is)
> what it is because it's also the answer for my employer owned workstation,
> production machine etc.  or the other way around ?  Should I use good
> practice
> at home because it's good practice, or should I use good practice only at
> work
> because it only matters there ?

  In a home environment, where you do not have other users accessing the 
system, then root is probrably the best route, and not sudo.

  A) We assume you know what your doing, and don't need it logged.
  B) We assume that if someone does hack the machine, they're going to go for 
root, and *NOT* sudo.

  There is also the fact that a machine machine is much more likely to 
get 'hacked' then in a corperate environment.  If you have things setup to 
sudo, you may then be more suseptable, becouse instead of attempting to hack 
root, they can hack you, and have root access to whatever you are sudo on.  
Granted, it's logged somewhere, but not to many people with home machines 
regularly monitor their logs..

--- 
Thomas Charron
<< Wanted: One decent sig >>
<< Preferably litle used  >>
<< and stored in garage.  ?>>

**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to