inetd is probably monitoring the telnet port and calling /usr/sbin/tcpd
which does the dns lookup to check for spoofing before calling telnetd
(see inetd.conf). But I would think that inetd would be doing the same
thing for rlogin. In any case, you could comment out that record in
inetd.conf, restart inetd and start telnetd, than try to telnet to it.
-Robert
> This didn't prevent telnet for forcing a dialout. However, further
> experimenting showed that rlogin does _not_ force a dialout. I glanced
> very briefly at some of the RFCs and man pages. Apparently, rlogin came
> to life later than telnet, but the man page for rlogin says that telnet
> will replace it shortly. Can't really see there's much difference in the
> two.
>
> Seems a shame to have to resort to setting up a DHCP/DNS server just to
> prevent a dialout on telnet. I was hoping to make the server headless
> and use telnet or ssh to talk to it without a lot of fuss. I still can't
> surf from a workstation on the network, but that's another story.
>
> Paul
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:51:30 EDT