Re: ssh-vs-rsh benchmark result
On Wed, Aug 28, 2002 at 11:04:43AM -0400, Sean Dague wrote:
> On Tue, Aug 27, 2002 at 06:37:10PM +0900, Junichi Uekawa wrote:
> > ... and for a 0.1-second computing task of obtaining the load average
> > of hosts, running through 1000 computer nodes, it will make a big
> > difference.
> But in that case why are you using ssh or rsh for that purpose, when
> something like ganglia or pcp will provide you that information nearly
> continuously with very little overhead.
You never know when you might want to run something on all hosts. It's
useful to have the capability of doing it quickly. You might not make use
of it often, so it might not be all that useful, but rsh has non-zero utility.
rsh is totally insecure against someone who is on the same ethernet segment
as you, so if someone sneaks into your computer room and attaches a wireless
LAN (802.11b) hub to your network, they could log into your machines, from a
laptop, while they sit outside your building). This is an unlikely attack,
unless there is sensitive data on your computers. Other than copying your
data, or (more insidiously) corrupting it to make your calculations give
incorrect results, there is little to gain by such an attack. There is also
a large chance of getting caught (compared with remote attacks over the
Internet), since someone would have to physically break into your room.
That probably limits the suspects to students at your university, or
employees at your company, or personnel on your military base, etc.
If that sort of attack is not a big concern, then it is probably worth it
to have rsh set up.
Also, nobody has pointed out some of the things you can do with ssh that
you can't do with rsh. With ssh, you can create a keypair, and put the
public key in the authorized_keys file on any host you want to be able to
log in to using the private key. The cool part is that you can limit that
key to running only a certain command. The advantage is that you can
automate tasks that need root on remote machines without allowing
passwordless root shell logins in general. Read more in
sshd(8): AUTHORIZED_KEYS FILE FORMAT.
One advantage of always using ssh is that you get used to using it, so you
don't so much time trying to remember its quirks when you need to log in
over an insecure network (so you can't use the more familiar rsh). This
applies more to using scp instead of ftp, because ssh by itself is pretty
much identical to rsh, and not very quirky :)
#define X(x,y) x##y
Peter Cordes ; e-mail: X(email@example.com. , ns.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BCE