From owner-freebsd-stable Tue Feb 27 18:33: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id AB1BD37B719 for ; Tue, 27 Feb 2001 18:33:03 -0800 (PST) (envelope-from mike@sentex.net) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.2/8.11.1) with ESMTP id f1S2Wpf19539; Tue, 27 Feb 2001 21:32:51 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.2.1.0.20010227163349.01fed070@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 27 Feb 2001 16:44:24 -0500 To: "Thomas T. Veldhouse" , "Chris Faulhaber" From: Mike Tancsa Subject: Re: SSH1 fixed yet? Cc: In-Reply-To: <041d01c0a103$14732c40$3028680a@tgt.com> References: <5.0.2.1.0.20010227145510.02f3c2c0@marble.sentex.ca> <031e01c0a0f8$92cdac60$3028680a@tgt.com> <20010227154421.A23941@peitho.fxp.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:18 PM 2/27/01 -0600, Thomas T. Veldhouse wrote: >FWIW - I just did a CVSUP and the only changes were against the kernel (many >of those - some of which are networking related) and some manpages in bind >and some configuration file changes. > >Now I can connect with SSH1 again. It does appear the problem was related >to a kernel change. Yes, as I posted yesterday, this was my experience as well... ---Mike >Delivered-To: freebsd-stable@freebsd.org >Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) > by hub.freebsd.org (Postfix) with ESMTP id 9D0C237B4EC > for ; Mon, 26 Feb 2001 15:49:21 -0800 (PST) > (envelope-from mike@sentex.net) >Received: from chimp (fcage [192.168.0.2]) > by cage.simianscience.com (8.11.2/8.11.2) with ESMTP id f1QNnIg19682 > for ; Mon, 26 Feb 2001 18:49:20 -0500 (EST) > (envelope-from mike@sentex.net) >Message-Id: <4.2.2.20010226184447.03e1ac58@marble.sentex.net> >X-Sender: mdtancsa@marble.sentex.net >X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 >Date: Mon, 26 Feb 2001 18:49:18 -0500 >To: stable@FreeBSD.ORG >From: Mike Tancsa >Subject: Re: ssh1 broken on today's snapshot ? >In-Reply-To: <5.0.2.1.0.20010226154525.0258ec70@marble.sentex.ca> >Mime-Version: 1.0 >Content-Type: text/plain; charset="us-ascii"; format=flowed >Sender: owner-freebsd-stable@FreeBSD.ORG >X-Loop: FreeBSD.ORG >Precedence: bulk >X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (amavis.org) >X-UIDL: #;n"!nI>"!gTG!!C^["! > > >OK, some more 'findings'... If I run it in debug mode, all goes as >expected. However, run on its own as a daemon, I actually eventually do >get through eventually after 60 seconds... This sounds suspiciously like a >DNS issue, but I dont see why it would be the case as all authoritative >servers have both an A record and PTR record. > >Now here is an even stranger result. If after killing the daemon, and then >running it once in debug mode, restarting the daemon (/usr/sbin/sshd), the >version 1 protocol connects work as expected! > >..... > >OK, Just finshed a make world and rebooted. Now everything works as >expected. Was there something peculiar about the Feb 26th snapshot ? > > ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message