CC,
If I am not mistaken 'make' will run the makefile script and then spit
out a blazingly fast string of code on the screen...
Running that as root is very dangerous because there could be hidden
exploit "code" hidden within that makefile by unscrupulous coders or by
crackers that might break into a CVS depository. (Which has happened at
least two times this past year.)
I do know that you shouldn't run any script without checking through it
to make sure nothing like that could be in there. Some of those files can
be thousands of lines long, written in an obscure fashion and it could
take you hours to determine whether or not it is entirely safe to run.
So, most people simply run those (I have done that myself and I am more
then certain that you have done as well.)
Now, bearing that in mind, are you 100% sure that by logging in and
running everything as root (likely makefiles too) hasn't possibly left
any or all of your systems open with hidden backdoors and such? (Most of
those "installs" of backdoors would fail if you ran the makefile as an
unprivaleged user, but you would know that being that you have
administrated *NIX systems for 10 years.)
It is simply the most wise of *NIX administratrion practices to never
bring up a full desktop in any *NIX as the root user, unless there is
absolutely no other choice. (Which I believe is a true impossibility.)
As for your question, I have never come across any X-lock-like
application that will run as root. Perhaps if you setup something to log
the output of what is happening when you attempt to run 'X-lock' as root,
then you could peruse the file and determine what the error is.
Regards,
Robert Adkins II
IT Manager/Buyer
Impel Industries, Inc.
Ph. 586-254-5800
Fx. 586-254-5804
-----Original Message-----
From: Red Hat [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 8:26 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Robert Adkins
Subject: RE: Screensavers as root
Well I have been running Unix systems for over 10 years and been using
linux since kernel 0.97 and I have NEVER mad a mistake because I was
logged in as root. If you are prone to do that, maybe you chose the wrong
career.
Anyway, is there an alternative to xlock on RH 8.0?
Thanks,
CC
-----Original Message-----
From: Jan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 8:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Screensavers as root
Robert Adkins wrote:
> NEVER LOGIN DIRECTLY AS ROOT. Especially a full X-Windows desktop.
>
> There are many other things that you can do to run those apps as
some
> other user. There is setting the SUID bit on those programs. (Which is
> always a winner, except that you need to read up on any potential
> security issues in doing so with the apps you need to run.)
>
> Running as root can lead to a serious mishap that will ruin your
[... etc etc etc]
>
One of the nice things about Linux is that you can do whatever you like
- even if it isn't a good idea. It is still true that UNIX is an
operating system for grown ups - IOW: there is no nanny to tell you what
you can and can't do. The assumption is that you know what you are doing
- ie, if you do something risky, you take extra care.
Having said that - I wouldn't mind being told this particular bit of
information rather than having to hope that I will one day stumble over
it in whichever obscure place RedHat have found good to place it this
time. This is after all Linux, not Windows. Knowledge is to be
considered good. Or is this viewpoint too subversive?
/jan
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
----------
This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
contain viruses. The sender therefore does not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of e-mail transmission. If verification is required please request
a hard-copy version.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
