From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 5 08:46:47 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F217016A4BF for ; Fri, 5 Sep 2003 08:46:47 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-107-253.dsl.lsan03.pacbell.net [64.169.107.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1808343FB1 for ; Fri, 5 Sep 2003 08:46:47 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id AA8E166B04; Fri, 5 Sep 2003 08:46:46 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 865A7A5B; Fri, 5 Sep 2003 08:46:46 -0700 (PDT) Date: Fri, 5 Sep 2003 08:46:46 -0700 From: Kris Kennaway To: Dwayne MacKinnon Message-ID: <20030905154646.GA59881@rot13.obsecurity.org> References: <3F589E94.1080508@xwave.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <3F589E94.1080508@xwave.com> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org Subject: Re: PUzzling sshd behaviour X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2003 15:46:48 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 05, 2003 at 10:32:52AM -0400, Dwayne MacKinnon wrote: > Anyone else see this type of thing before? I did some research on the=20 > lists but all I ever saw was a problem with reading resolv.conf. That's= =20 > not the case here, because it's definitely picking up the nameserver=20 > from that file. The fact that sshd requires reverse IP resolution is well-known behaviour. It's probably the most common FAQ about sshd ("Why is my login taking 60 seconds to present the password prompt?"). Kris --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/WK/mWry0BWjoQKURAlc7AKDjrRH4Ha/Rq7Pv1vpT5z7NEb2LRQCg4oum vzA6RE94P5aSrnyNyNVOOcs= =1APm -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--