The moving of the alias can even be done automagically if you add
--with-rsh=/bin/rsh or something close during the configure stage.
As for installation, if the old rlogin works, then so should rcp.
Is rdist already installed on the end machines? It can copy the files +
links with permissions intact, and even edit your startup scripts to start
sshd (and nuke rlogin!)
Sean
At 11:51 AM 4/22/1999 +1200, [EMAIL PROTECTED] wrote:
>
>> SSH doesn't seem to be such an easy replacement either. I tried to
rlogin to
>> an ssh server and the protocols are not compatible.
>>
>> Tiamat:~> rlogin somehost.with.ssh.com
>> SH-2.0-2.0.12 (non-commercial)
>> Tiamat:~>
>>
>> It would be a painstaking task to install SSH clients for all the computers
>> around here and change the way all the software works.
>
>You don't need to change the way the software works. When SSH is
>installed, it also creates an alias called slogin. mv'ing this alias to
>rlogin will give you a secure rlogin drop-in replacement, no software
>changes required. That doesn't help on the installation front tho :/
>
>Richard
>
>
>
>
>_______________________________________________
>Masq maillist - [EMAIL PROTECTED]
>http://tiffany.indyramp.com/mailman/listinfo/masq
>Admin requests can be handled by web (above) or
[EMAIL PROTECTED]
>
------------------------------------------------------------
Sean Walberg <[EMAIL PROTECTED]> http://www.escape.ca/~sean
PGP (RSA & DSS) on keyservers ICQ: 762966
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
