Date: Sun, 20 Feb 2000 13:22:15 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: openssl in -current Message-ID: <20000220132215.F14682@dragon.nuxi.com> In-Reply-To: <Pine.BSF.4.21.0002191942240.2430-100000@freefall.freebsd.org>; from kris@FreeBSD.org on Sat, Feb 19, 2000 at 07:46:50PM -0800 References: <38AF5F59.A0BEC49@gorean.org> <Pine.BSF.4.21.0002191942240.2430-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 19, 2000 at 07:46:50PM -0800, Kris Kennaway wrote: > > Having _a_ general-purpose cryptography toolkit in the base system allows > us to add in all sorts of cool things to FreeBSD (https support for fetch, > openssh, random cryptographic enhancements elsewhere). Which OpenBSD has done -- so why was it so easy for them? They have the *same* rules to live by that we have -- even though they are Canadian, the rsaref libs came from USA, thus they cannot be exported from Canada. It sounds like we just need to do more engineering -- maybe step back from the issue and look to see if we took a wrong turn in the way we've set things up. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000220132215.F14682>