home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.security.misc
- Path: sparky!uunet!elroy.jpl.nasa.gov!lambda.msfc.nasa.gov!news
- From: palmer@Trade_Zone.msfc.nasa.gov (Paul (Cliffy) Palmer)
- Subject: Re: They forget rusers, was Re: reasons for
- Message-ID: <1992Dec12.010422.20706@lambda.msfc.nasa.gov>
- Sender: news@lambda.msfc.nasa.gov (Newsmaster)
- Nntp-Posting-Host: isabella.msfc.nasa.gov
- Reply-To: palmer@Trade_Zone.msfc.nasa.gov
- Organization: New Technology, Inc.
- References: <Bz3y3E.Jyu@avalon.nwc.navy.mil>
- Date: Sat, 12 Dec 1992 01:04:22 GMT
- Lines: 25
-
- In article Jyu@avalon.nwc.navy.mil, dejesus@archimedes.nwc.navy.mil (Francisco X DeJesus) writes:
- >In article <1992Dec9.173938.8706@nntp.hut.fi> jkp@cs.HUT.FI (Jyrki Kuoppala) writes:
- >
- >Still, doesn't rusers (and rup, rlogin, rsh, etc) require a hostname? If
- >they don't work with IP addresses (they way finger/telnet can) then their
- >use is restricted if the machine you are trying to "probe" isn't registered.
- >Anyone know of a way around this (other than making a local entry in your
- >hosts file)?
- >
-
- rusers the program does require a hostname, although the rusers (RPC)
- protocol does not. If you have written an RPC program it is fairly
- trivial to rewrite the rusers command to accept IP addresses. I
- suspect that rlogin and rsh have a similar problem, although they are
- not RPC programs. It should just be a simple matter of getting the
- source and modifying it to accept IP addresses.
-
- For another approach, some vendor's systems support an environment
- variable that can be set to the pathname of a "local" host table. This
- allows users to augment the hostname lookups to include all of their
- favorites...
-
- ---
- Paul (Cliffy) Palmer
-
-