indeed. this worked nicely. i'm not sure why i have the allow at the end of the line :P i took it out. i run sshd as a daemon. is there any reason for me to run inetd if i don't allow telnet or ftp? inetd doesn't control bind and postfix right? i'd like to lock down those two servers as much as i can. matthew [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Shirley Sent: Monday, December 04, 2000 12:57 PM To: [EMAIL PROTECTED] Subject: RE: [expert] sshd and simple networking That should be "sshd:" instead of "in.sshd:" HTH, Bill PS. Why to have a ": ALLOW" at the end of the line? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of SIR admin Sent: Monday, December 04, 2000 9:53 AM To: expert Subject: [expert] sshd and simple networking i'm trying to get sshd working. it's not accepting connections. :/ here is the error message i get. i have a feeling it's the way my hosts.allow/deny files are set up. can anyone give me a hand? ssh_exchange_identification: Connection closed by remote host my hosts.allow file: in.sshd : ALL 192.168.100. 192.168.1. : ALLOW in.telnetd : LOCAL : ALLOW ~ my hosts.deny file: ALL : ALL EXCEPT localhost : DENY i can telnet to this machine, but not ssh. now i know that i have the hosts.deny folder to deny everything but the localhost, but even when i remove that line it still harrasses me. on the same note, does anyone know any good how-tos on hosts.allow and hosts.deny and thier formats and the like. sorry if this e-mail is greek...i'm getting a T-1 installed and my head is spinning. they just "accidently" pulled the plug on our SCOdb server. argh! matthew sys/net admin [EMAIL PROTECTED]
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
