-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For /etc/hosts.allow the proper syntax is
in.telnetd: ALL Check /etc/inetd.conf to be sure that the line referring to in.telnetd is not commented out. If it is you'll want to uncomment it and send a `kill -HUP <pid of inetd>' to restart inetd and make it reread /etc/inetd.conf-*+, where you substitute inetd's pid into the command. However, this defeats the security you are trying to achieve by using ssh. ssh is a different protocol that achieves some of the same functionality of telnet. It also listens on a different port. Why don't you just install a ssh client on your pals windoze box? For instance ssh windows client ( you can find it on one of our servers http://slug.ceca.utc.edu ). Charles H. Baker Manager Student Microcomputer Labs [EMAIL PROTECTED] http://www.utc.edu/StudentMicroLabs/ Are you using PGP? Why not? PGP for a more secure 'Net. - -----Original Message----- From: Drew Parsons [mailto:[EMAIL PROTECTED] Sent: Friday, November 05, 1999 3:11 PM To: debian-laptop@lists.debian.org Subject: Re: potato security ;( On Fri, Nov 05, 1999 at 11:06:52AM -0500, Thomas Vogels wrote: > As others have pointed out, this is not an ssh problem. The > configuration of the /etc/hosts.* file should allow you to telnet > to your machine. But then, you _should'nt_ use telnet. > Try 'ssh -v' and let us know what ssh is unhappy about. > Have you looked into /etc/hosts.equiv (bad) and > /etc/ssh/shosts.equiv (good)? <<SNIP>> So can anyone tell me what I'm doing wrong with telnetd and hosts.allow? I've got in.telnetd: ALL: allow set, but still no luck. By the way, in.telnetd does not seem to be actually running, but inetd is. I think the latter calls up the former when needed, so I don't believe this is the problem. <<SNIP>> -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com> iQA/AwUBOCNv/b6VX5TWBNfUEQLSCACgn+cXtXVNGuBmvep7QpeVUWAonNMAmwe6 HU9rOG5huL/syHWrXGAXSMTA =tRFD -----END PGP SIGNATURE-----
