From owner-freebsd-security Sun Jan 2 23:28:42 2000 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5EE6D14D0F; Sun, 2 Jan 2000 23:28:40 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id CAA07950; Mon, 3 Jan 2000 02:28:33 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Mon, 3 Jan 2000 02:28:33 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: David Rankin Cc: Brian Fundakowski Feldman , "Michael H. Warfield" , Dug Song , security@FreeBSD.org, openssh-unix-dev@mindrot.org Subject: Re: OpenSSH protocol 1.6 proposal In-Reply-To: <20000102061545.A1691@rumpole.bohemians.lexington.ky.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 2 Jan 2000, David Rankin wrote: > Speaking completely without facts, I am personally skeptical about > enhancing the 1.x protocol when all of the standards processes are > focused on getting 2.0 out the door. That said, I am willing to be > convinced on the matter. I agree entirely. I'd love to see a free, BSD-licensed, SSH 2.x implementation out there. The continuing emphasis on improving the non-standard, albeit widely deployed, SSH 1.x protocol seems to be a less useful allocation of resources. While a free version of 1.x is extremely useful, it's not the end-all. :-) If you can get people to upgrade to modified 1.x with backwards compatibility, wouldn't you be better served getting them to upgrade to 2.x with backwards compatibility? :-) Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message