home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!gumby!destroyer!cs.ubc.ca!bcsystems!ewilts
- From: ewilts@galaxy.gov.bc.ca (Ed Wilts)
- Newsgroups: comp.security.misc
- Subject: Re: They forget rusers, was Re: reasons for
- Message-ID: <1992Dec13.153543.1351@galaxy.gov.bc.ca>
- Date: 13 Dec 92 15:35:43 -0800
- References: <Bz3y3E.Jyu@avalon.nwc.navy.mil> <1992Dec12.010422.20706@lambda.msfc.nasa.gov>
- Organization: BC Systems Corporation
- Lines: 26
-
- In article <1992Dec12.010422.20706@lambda.msfc.nasa.gov>, palmer@Trade_Zone.msfc.nasa.gov (Paul (Cliffy) Palmer) writes:
- > 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.
-
- This is implementation-specific information you are passing on here. My
- rusers, rlogin, and rsh programs will happily accept an IP address as well as
- fully qualified domain names.
-
- --
-
- Ed Wilts, BC Systems Corp., 4000 Seymour Place, Victoria, B.C., Canada, V8X 4S8
- EWilts@Galaxy.Gov.BC.CA Office: (604) 389-3430 Fax: (604) 389-3412
-