Path: utzoo!mnetor!uunet!mcvax!prlb2!kulcs!dannyb From: dannyb@kulcs.uucp (Danny Backx) Newsgroups: comp.protocols.tcp-ip Subject: Re: rsh equivalent Message-ID: <102@icarus.kulcs.uucp> Date: 10 Mar 88 06:56:11 GMT References: <23511@hi.unm.edu> Reply-To: dannyb@kulcs.UUCP (Danny Backx) Organization: Katholieke Universiteit Leuven, Dept. Computer Science Lines: 37 Keywords: rsh In article <23511@hi.unm.edu> cyrus@hi.unm.edu (Tait Cyrus) writes: > >I am looking for PD version of code that accomplishes the same thing >as rsh but conforms to the RFC's (machine name case independent). >We have users who like to pipe BIG jobs from one machine to another >machine via rsh's. > >The reason I am interested in something other than rsh is because >here at UNM we are strongly considering disallowing the r* programs >(rsh/rcp/rlogin) because they do NOT conform to the RFC's as well >as being BIG security problems (.rhosts). You might want to look at the "rex" service in SUN's RPC package. This is something quite similar to rexec(3) and rsh(1). What I mean is : it also doesn't provide a virtual terminal for your remote processes. If you have access to SUN manuals, look at on(1c), rexd(8c), and rex(3r). If not, you could get the idea by looking in the RPCSRC 3.9 package, which was recently posted to the net (comp.sources.???). It is also accessible via anonymous ftp and via Email from the archives of Sun-Spots. If you need better authentication than BSD's r*, I think this may do : the rex-system uses the same "UNIX-style authentication" that the entire RPC package uses. If you have a SUN or a 4.3 system from Mt.Xinu, you should be able to use it right away. Danny Backx -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Danny Backx | mail: Katholieke Universiteit Leuven Tel: +32 16 200656 x 3537 | Dept. Computer Science E-mail: dannyb@kulcs.UUCP | Celestijnenlaan 200 A ... mcvax!prlb2!kulcs!dannyb | B-3030 Leuven dannyb@kulcs.BITNET | Belgium