Path: utzoo!mnetor!uunet!husc6!necntc!ima!think!barmar
From: barmar@think.COM (Barry Margolin)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: rsh equivalent
Message-ID: <18184@think.UUCP>
Date: 19 Mar 88 12:44:32 GMT
References: <23511@hi.unm.edu> <102@icarus.kulcs.uucp> <3647@bloom-beacon.MIT.EDU> <1188@kulcs.kulcs.uucp> <722@kaos.UUCP>
Sender: usenet@think.UUCP
Reply-To: barmar@fafnir.think.com.UUCP (Barry Margolin)
Organization: Thinking Machines Corporation, Cambridge, MA
Lines: 16
Keywords: rsh trusted ports

In article <722@kaos.UUCP> romkey@kaos.UUCP (John Romkey) writes:
>"Trusted ports" (when port numbers less than 1024 can only be used by
>a trusted user) exist only in the world of the Berkeley UNIX TCP.
>Virtually no TCP/IP implementations that are not derived from BSD
>UNIX have the concept of "trusted ports"; they will allow any user
>program to open a connection on any port that isn't already in use.

This is why the Unix RSH server also checks the host against a .rhosts
file.  Presumably you would only list machines that implement the
trusted port rule.

Barry Margolin
Thinking Machines Corp.

barmar@think.com
uunet!think!barmar