From owner-freebsd-current Thu Feb 24 10:31:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 3673337BDCB for ; Thu, 24 Feb 2000 10:31:50 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA417544; Thu, 24 Feb 2000 13:31:41 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <94538.951377875@zippy.cdrom.com> References: <94538.951377875@zippy.cdrom.com> Date: Thu, 24 Feb 2000 13:32:00 -0500 To: "Jordan K. Hubbard" , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Heads up! OpenSSH is about to enter the tree. Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:37 PM -0800 2/23/00, Jordan K. Hubbard wrote: >Since it came down to making openssl actually useful for something or >taking it out of the tree, we accelerated progress somewhat on the >openssh integration work. Sounds like a good idea. >I will also be delaying -current's release date until March 10th in >order to give this more proper testing. I think it's worth the wait to have openssh included. One minor thought. In OpenBSD there is still a port for ssh1, and they have it so the port for ssh1 starts that up on port 2022. We (at RPI) have found a few ssh clients that do not work well with openssh, and I think it would be a good idea to do something similar to what openbsd did with the port for ssh1. (maybe not exactly the same -- maybe have it just some messages that the ssh1-build process will print out so people are aware of that option. 4.0-release wouldn't have to wait for those adjustments to the ssh1 port, of course) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message