From owner-freebsd-security Thu Jul 25 16: 8:24 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 107F537B400 for ; Thu, 25 Jul 2002 16:08:22 -0700 (PDT) Received: from server1.wojo.com (server1.wojo.com [66.36.30.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89C5A43E9C for ; Thu, 25 Jul 2002 16:08:21 -0700 (PDT) (envelope-from robertw@wojo.com) Received: by server1.wojo.com (Postfix, from userid 502) id D47E63B2D; Thu, 25 Jul 2002 19:08:20 -0400 (EDT) Received: from moe.wojo.net (localhost [127.0.0.1]) by server1.wojo.com (Postfix) with ESMTP id 5857E3A82 for ; Thu, 25 Jul 2002 19:08:16 -0400 (EDT) Subject: RE: Openssh-portable MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 25 Jul 2002 19:08:13 -0400 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-Has-Attach: content-class: urn:content-classes:message X-MS-TNEF-Correlator: Thread-Topic: Openssh-portable Thread-Index: AcIzfp5kjzchheQCSVCW/Nih2DMH6wAsOWuQ From: "Robert S. Wojciechowski Jr." To: X-Spam-Status: No, hits=-1.4 required=7.0 tests=USER_IN_WHITELIST_TO,AWL version=2.40 X-Spam-Level: X-Sanitizer: Anomy Sanitizer Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Take a look at: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D39953 There is now a patch to fix this without the resolv.conf workaround. - Robert > I just set up openssh-portable-3.4p1_5 from the ports on a 4.5-RELEASE box > and now ssh is very slow to login (60 seconds or more). Other than the > delay, everything else works fine. I couldn't find any answers in the > archives. >=20 > Seems like DNS lookup issue. >=20 > Is this a known problem and what is the suggested fix? >=20 > Thanks. >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message