From owner-freebsd-current Tue Mar 7 9:42:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1A98837B9C4 for ; Tue, 7 Mar 2000 09:42:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA91664; Tue, 7 Mar 2000 09:39:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-reply-to: Your message of "Mon, 06 Mar 2000 01:10:30 +0100." <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> Date: Tue, 07 Mar 2000 09:39:52 -0800 Message-ID: <91661.952450792@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. :-( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message