Subj : Re: su on startup
To   : comp.os.linux
From : michael1cat
Date : Sun Aug 15 2004 12:09 am

lzman@mindless.com (gnosis) wrote in message news:<db0378b2.0408121450.5041ce7@posting.google.com>...
> I am the only user on my system and I want root capabilities without
> having to login as root.  I want to run su when I login but I dont
> want my password to be in raw text anywhere. Is it possible to input
> the password to su encrypted?

Configure sudo.  If you want, you can configure it so you can go
from your ID to root's, without needing to give your password again.
Then, when you want to become root, all you need to is:
$ sudo su -
or for a one-way trip (and to save an extra process):
$ exec sudo su -

Note that are a few zillion reasons why one shouldn't operate as
superuser (root) except when it is actually required.  A tiny subset
of those reasons include:
An error done as root can destroy an entire system, whereas an
error done as a normal user typically only risks stuff that ID
can access/alter.
Actions which lead to stuff inappropriately owned by root (e.g.
unnecessary/excessive operation as root) can lead to substantial
later difficulty in determining what proper belongs to the operating
system or specific application(s) vs. what belongs to specific
user(s) (these situations can, for example, significantly complicate
cleanups/upgrades/backups/restores).

In both my personal and work environments, to the extent feasible I
avoid doing work as root when it's not necessary to be root to do
that work.  I also generally make it as easy as possible for myself
to "drop privilege" (do work under my own ID rather than root's)
and switch back to using root privilege again if/where needed,
so I have generally no reasons/excuses to prevent me from
dropping privilege at any and all appropriate times.  Of course
how easy it is to first get that root privilege may vary radically
depending on environment and security considerations and such,
but the general idea is, only use root when necessary and
appropriate, and try to facilitate that it's only used then.

And I do have over 10 years of production UNIX support (and over six
years LINUX experience).

Also, on LINUX, one might find it convenient to use a separate
virtual console or window for stuff done as root.  That can also
make switching back to a non-root window/console session (and
back again when required) pretty convenient and easy.

.