Thanks for all the helpful responses from:
Doug Johnson <drjohn_at_pizero.Colorado.EDU>
Anthony Talltree <aad_at_nwnet.net>
System Prestidigitator <BOLSON_at_frango.hs.washington.edu>
Mike Iglesias <iglesias_at_draco.acs.uci.edu>
Skeate, Scott B <scott.b.skeate_at_lmco.com>
Nathan Grass <NathanG_at_UTS.Itron.com>
Consensus seems to be to not move the system-supplied rsh and rlogin
binaries, and instead put ssh before them on the search path (eg, in
/etc/csh.cshrc). This does fix the problem. Or, if I don't want to alter
the path, another solution might be to define command aliases in
csh.cshrc so that a user typing "rsh" gets ssh instead.
Graham
--- original message ---
I'm wondering if anyone has had any success using ssh to replace rsh and
rlogin services, on Digital UNIX 4.0D.
To fill in the background, this works by moving the system-supplied rsh
and rlogin programs to a new location (such as /usr/local/sbin, for
example).
ssh then installs links for rsh and rlogin which point to itself, so
that users invoking rsh/rlogin actually get ssh. If the remote system
doesn't support ssh, then the original rsh/rlogin binaries get run.
This works just fine for the rlogin command.
Unfortunately, rsh seems to call rlogin itself - trying to run it from
its original location ion /usr/bin. So it fails with a message like:
>rsh hostname
Secure connection to (hostname) refused; reverting to insecure method.
Using rsh. WARNING: Connection will not be encrypted.
/usr/local/sbin/rsh hostname -l username
rsh: can't exec /usr/bin/rlogin.
^^^^^^^^^^^^^^^ naturally, since it's been moved.
Is there any simple way to defeat this?
Or a different way to set up ssh to achieve to same result?
Received on Tue Jun 23 1998 - 18:39:42 NZST