RH AS 2.1 Trusted network

[Miran Lampe_1]

Hi anyone.

I have installed RH AS2.1 on two Proliant servers. Because of clsuter requirements trusted networking between two nodes should be established.
I have properly setup xientd setings for rsh, rlogin, rpc and other netwokr services. IPTABLES are disabled hosts.equiv and .rhosts files are set also as needed. But anyway there is sam authentication problems( eg. rlogin asks for password, rsh hostname ls returns premition denied ...) What could be the problem? Can anyone halp me?

[Jochen Heuer]

Check hostname resolution. On the server try to do reverse lookup on the IP address you try the rsh from and make sure the *exact* name is in .rhosts and / or hosts.equiv ...

Regards,

Jochen

[Vitaly Karasik_1]

if I understand properly, you need to allow rcp, rlogin, etc for root

try these steps:

- chkconfig rlogin on
rsh on

- echo "rsh" >>/etc/securetty
echo "rlogin" >>/etc/securetty

- put your second_server_hostname into .rhosts

[Miran Lampe_1]

Thaks.

chkconfig resolves the problem
All r command now works properly

[Steven E. Protter]

eeeeeek!
You're using r protocols like rlogin and rsh on a "trusted" network.

Let me tell you, I would not trust that network.

The Berkley r protcols are not secure.

You can configure the secure shell protocols to provide the exact same functionality with real security if you generate and pass public keys.

ssh = rlogin
scp = rcp

I highly recommend it.

I've successfully done it with three HP servers at work and 2 Linux servers at my home office. I've even tried to allow it from the work to home office environment but am running into firewall configuration issues.

I've attached a document, which I modified to that gives you the entire process.

It's not THAT hard and the end product is a secure one.

[Steven E. Protter]

eeeeeek!
You're using r protocols like rlogin and rsh on a "trusted" network.

Let me tell you, I would not trust that network.

The Berkley r protcols are not secure.

You can configure the secure shell protocols to provide the exact same functionality with real security if you generate and pass public keys.

ssh = rlogin
scp = rcp

I highly recommend it.

I've successfully done it with three HP servers at work and 2 Linux servers at my home office. I've even tried to allow it from the work to home office environment but am running into firewall configuration issues.

I've attached a document, which I modified to that gives you the entire process.

It's not THAT hard and the end product is a secure one.