From owner-freebsd-current Wed Mar 8 3:28:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id E93B337B590 for ; Wed, 8 Mar 2000 03:28:22 -0800 (PST) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mail.originative.co.uk (Postfix) with ESMTP id A251C1D131; Wed, 8 Mar 2000 11:28:21 +0000 (GMT) Message-ID: <38C63963.AA114CF8@originative.co.uk> Date: Wed, 08 Mar 2000 11:28:35 +0000 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: <91661.952450792@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > I have upgraded a machine to the latest -current snapshot (it > > was running a -current from the end of January before). Every- > > thing went fine, except for one thing: ssh didn't work anymore. > > It used to work fine before. > > You really need to read the -current mailing list if you're going to > run -current. Saying that openssh took you by surprise as a -current > user is sort of like saying you didn't know Elvis was dead. :-( but he isn't! He was working in a chip shop last I heard. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message