From owner-freebsd-security Sun Jan 2 22:53:37 2000 Delivered-To: freebsd-security@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 42F5D14D34 for ; Sun, 2 Jan 2000 22:53:28 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id PAA24851; Mon, 3 Jan 2000 15:53:21 +0900 (JST) To: Garance A Drosihn Cc: security@FreeBSD.ORG In-reply-to: drosih's message of Sun, 02 Jan 2000 12:20:34 EST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: OpenSSH protocol 1.6 proposal From: itojun@iijlab.net Date: Mon, 03 Jan 2000 15:53:21 +0900 Message-ID: <24849.946882401@coconut.itojun.org> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>First of all, allow me to thank you for all of the work you have done >>maintaining OpenSSH for FreeBSD. I am looking forward to its entry >>into the base tree. (I'm also planning to convert from SSH to OpenSSH >>on all my systems as soon as it is feasible.) >> >>That said, the prospect of having a FreeBSD specific branch of OpenSSH >>disturbs me. I manage an extremely heterogeneous Unix environment and >>eventually hope to have OpenSSH running an all of my systems. I'm not sure which one to add my $0.02, but anyway I throw in mine. *Please do not split, or make freebsd branch on, openssh repository.* Splitting repository will chew up developers time by merging efforts, patching back and forth, and other branch-synchronize-again efforts. Use developers' time for real development, not for repository synchronization. Brian, make sure your changes go back to openssh repository (openbsd src/usr.bin/ssh), and not anywhere else. Make sure you work with openssh people. If you have problem (personal, framewar, whatever) directly contacting openssh guys, try to find someone help you do that. I have no particular opinion about protocol improvement, but please be sure to (1) get your change reviewed by as many guys as you can before go in (of course, including openssh folks) as it is security protocol issue, and (2) make sure the change directly go back to openssh repository, not other place. I personally have no problem talking with theo. I agree I've seen him react to emails with strong word sometimes (to me and to others), but once you understand his concern and what he cares about (security and robustness I believe, but I may be wrong) communication becomes much easier. $0.02 from a guy burnt his lifetime with multiple *BSD IPv6 support:-) (*every* tiny little difference between *BSD really killing us!) itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message