Date: Fri, 10 Dec 1999 00:25:01 -0800 (PST) From: Kris Kennaway <kris@hub.freebsd.org> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: OpenSSL update Message-ID: <Pine.BSF.4.21.9912100021130.16837-100000@hub.freebsd.org> In-Reply-To: <Pine.BSF.4.10.9912100226450.21596-100000@green.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 10 Dec 1999, Brian Fundakowski Feldman wrote: > Why don't you want libssl, too? If we don't have that, then we'll > end up having to install the port for using SSL and there will be > redundancy (wasted space) and two copies of OpenSSL to maintain, > still. Since it wasn't going to be used immediately it was suggested to leave it out for now. However it doesn't seem feasible anyway. > > Since I'm flying back home to australia next tuesday, and we have a > > feature freeze for -current coming up, what I'll probably do is just > > import all of openssl into the international repository, and enable the > > build only for people who have defined USA_RESIDENT==NO. When I get back > > in January I can get the munged version (i.e. w/o RSA sources, optionally > > building with RSAREF) imported and enabled for US people, as well as > > solving the binary distribution problem. The alternative, given the > > feature freeze, seems to be to forgo any kind of enhanced crypto support > > in 4.x, which would suck. > > > > Sound okay to everyone? > > Sounds great. I hope this means I get to import OpenSSH! Due to the US export stupidity someone else would probably have to import it into internat so the actual code doesn't leave the US, but historically we seem to have allowed non-crypto commits once it's there (e.g. minor changes, etc). Kris 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?Pine.BSF.4.21.9912100021130.16837-100000>