From owner-freebsd-current@FreeBSD.ORG Tue Feb 26 12:18:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D5D4106566C for ; Tue, 26 Feb 2008 12:18:38 +0000 (UTC) (envelope-from mouss@netoyen.net) Received: from balou.adapsec.com (balou.adapsec.com [91.121.103.130]) by mx1.freebsd.org (Postfix) with ESMTP id D176713C4F2 for ; Tue, 26 Feb 2008 12:18:37 +0000 (UTC) (envelope-from mouss@netoyen.net) Received: from [192.168.1.65] (ouzoud.netoyen.net [82.239.111.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mouss@netoyen.net) by balou.adapsec.com (Postfix) with ESMTPSA id B9E4A3ACD828; Tue, 26 Feb 2008 13:18:35 +0100 (CET) Message-ID: <47C4039A.3060907@netoyen.net> Date: Tue, 26 Feb 2008 13:18:34 +0100 From: mouss User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Juraj Lutter References: <47C34D7E.1010305@netoyen.net> <6.0.0.22.2.20080225180357.025db140@mail.computinginnovations.com> <47C35CCC.9090300@netoyen.net> <47C3DDCF.6070109@gmail.com> In-Reply-To: <47C3DDCF.6070109@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Derek Ragona Subject: Re: ssh_exchange_identification: Connection closed by remote host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 12:18:38 -0000 Juraj Lutter wrote: > mouss wrote: >> >> I tried with secureCRT and with openssh from a netbsd, debian and >> centos boxes. same error. >> I googled for the error, and it seems popular! >> - I don't think it's an /etc/host* issue, as I was connected to the >> box multiple times (and I tried from multiple IPs). >> - I tried from a vmware hosts with no keys, just to make sure it's >> not a key issue. >> >> could this be a dns issue? the host is running a "caching" bind. I >> would prefer not to disable dns lookup, but if this causes trouble... > > > This seems to be more a /etc/hosts.allow issue. > I found the problem: fatal: /var/empty must be owned by root and not group or world-writable. I have created an account and set the home to /var/empty, but this changed the owner of /var/empty. sigh. I should have found http://www.darkknight.demon.co.uk/prdb/unix/ssh.html sooner ;-p thanks to all who responded.