[496] in Kerberos
Re: rcp - a non-trivial problem
daemon@TELECOM.MIT.EDU (jb%cs.brown.edu@RELAY.CS.NET)
Mon Sep 5 15:48:14 1988
From: jb%cs.brown.edu@RELAY.CS.NET
To: "Jeffrey I. Schiller" <jis@BITSY.MIT.EDU>
Cc: qjb@ATHENA.MIT.EDU, kerberos@ATHENA.MIT.EDU
In-Reply-To: Your message of "Mon, 05 Sep 88 13:38:56 EDT."
You only hit upon one problem that Jay(?) was having. His problem
was with rcp. Rcp never creates a login session on the remote machine.
By modifying rcp, Jay's problem can be fixed. Rcp currently handles
the third party transfers by doing an rsh to the src host and starting
up an rcp to the destination host. If rcp was modified to do the
transfer in two steps, it could work with "no" new authentication
problems. (The "no" is qualified because a new ticket will need to
be fetched.) The first transfer is to copy the src file to the
initiatiing machine. Next, copy the file to the destination machine.
There are some problems with this approach. First, there must be
enough disk space on the initiating machine to store the file temporarily.
The second problem is that there is twice as much network traffic
since the file is being transferred twice. The second problem
might be ignorable because I don't think third party transfers are
used much. (Was this the first time someone mentioned that a third
party rcp did not work under kerberos?)
Jim
