Sorry for butting in here, but that kind of answer is going to
get the Linux box placed out on the back porch.
I can't recommend installing ssh as *THE* answer when my shop
has 100+ *NIX servers that are not Linux and 3 machines that are. You
have to protect your machines as best you can with the tools
available (creative people included here) and keep some sense of
"common environment" and transparency.
What do you do with the machines that have Vendor Installed products
on them and the Vendors will NOT support the machine if you
load ssh or someother "restrictive" software. We tried to
load S3 last year and had to drop the entire project due to the
negative feedback from our vendors.
Or, you could treat your Linux box like you do your MS products
and buy/download/install some new product everytime you can't
figure out how to do something with the tools delivered with
the OS.
Please don't get me wrong, I do preach/practice security also.
NT didn't come with incoming telnet capabilities and still got
hacked quite frequently. Is ssh the cure there?
<soap box>
I think we should just answer the question asked, (which I did
off-list) and then make a suggestion like "You might want to check
into ssh" and give a couple of positive reasons why.
</soap box>
Have fun,
--
Rick L. Mantooth
[EMAIL PROTECTED]
So what's the speed of dark?
On Thu, 30 Dec 1999, Igmar Palsenberg wrote:
=>
=>
=> On Mon, 27 Dec 1999, Hiten Sonpal wrote:
=>
=> >
=> > Greetings,
=> >
=> > Does anyone know what needs to be done to enable rsh access for root? I'd
=> > like to be able to connect as root from host1 to host2 on our intranet
=> > without requiring a password. Setting up a .rhosts file in /root is not
=> > enough... I think I need to modify /etc/pam.d/rsh, but I'm not sure.
=>
=> Yes, but it is a VERY STUPID IDEA. Setup ssh with the keys. That has the
=> same functionality, but is a lot more secure..
=>
=> >
=> > Thanks in advance,
=> > -- Hiten
=>
=>
=> Igmar
=>
=>
=> --
=> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
=> as the Subject.
=>
=>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
