From owner-freebsd-ports Tue Nov 2 11:47:47 1999 Delivered-To: freebsd-ports@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7344F14D82; Tue, 2 Nov 1999 11:47:34 -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 NAA29570; Tue, 2 Nov 1999 13:46:45 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Tue, 2 Nov 1999 13:46:45 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , Kris Kennaway , security@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: OpenSSH patches In-Reply-To: <6891.941523712@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 1 Nov 1999, Jordan K. Hubbard wrote: > > Well, that is really the deciding point I think. So can you get a > > definite answer ? > > Yes, I'll work on this. Having ssh bundled into FreeBSD is pretty > important to me. And if this means OpenSSL bundled also? :-) Bundling apache-modssl would also be nice, as with K5, krbIV support versions of various packages, etc. BTW, "they" tell me that when the new crypto guidelines are released, the chances are they will also be friendly to open source. Hopefully "they" are right. (they being people appropriately placed in the process) I personally prefer the European arrangement where open source crypto is fine, but closed source is subject to limitations :-). I guess we shouldn't get started on the whole crypto export debate, but just to summarize the eventual conclusion: "It sucks". 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-ports" in the body of the message