Date: Wed, 1 Oct 1997 09:35:05 -0600 (MDT) From: Marc Slemko <marcs@znep.com> To: Eivind Eklund <perhaps@yes.no> Cc: chat@FreeBSD.ORG Subject: Re: Microsoft brainrot (was: r-cmds and DNS and /etc/host.conf) Message-ID: <Pine.BSF.3.95.971001092831.13876B-100000@alive.znep.com> In-Reply-To: <199710011154.NAA20125@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Oct 1997, Eivind Eklund wrote: > > SSL is, AFAIK, subject to certain undesirable licensing conditions (not > > exportable, not available for commercial use, etc.) which may render it > > unsuitable. > > SSLeay isn't too much subject to this; it was developed outside the > US. We'd need it integrated in a web-server, though, and I don't know > how the state of Apache-SSL is (Stronghold works just fine for my job, > so I haven't looked at the freeware side of this). Apache-SSL works fine. The main reason it isn't a standard part of Apache is because the US goverment are a bunch of twits. First, you have export restrictions. Even if software originates outside the US, if you import it and then try exporting it again you can get into trouble. Secondly, RSA has a patent on technology required to support SSL v2 which makes it illegal to use that within the US without a license from RSA. SSL v3 can be implemented using another algorithm; the pattent on that one expires soon if it hasn't already. I'm not sure what common clients support.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.971001092831.13876B-100000>