Re: continuous build failure in lib/libssl

["Todd T. Fries" <todd@fries.net>]

/usr/src/lib/libssl builds 'stub' functions for the patent problem code.
The sslUSA26.tgz and ssl26.tgz are built with their minor numbers one higher
than that of the /usr/src/lib/libssl libs .. thus enabling dynamically linked
code to ship on the cd, but the `enabled' crypto libs are downloaded by the
user..

The 'ports/security/ssl26' port is non-usa, dont use it if you're in the us.
The 'sslUSA26-port.tgz' is a tarball you download and extract and build only
if you're in the usa.  Use only if you have your licensing issues squared away.
Or wait till September.

Aren't crypto disabling licenses grand?

On Wed, Mar 29, 2000 at 04:15:45PM -0800, Luke Bakken wrote:
> So the source code in /usr/src/lib/libssl *does* include the patented
> routines, thus eliminating the need to get the src-patent.tar.gz file? OR,
> does the code in /usr/ports/security/ssl26 fill in the gaps, and you have 
> to do both to get a working system?
> 
> Thanks a lot for your help - I'm dying to get 'make build' to work!!
> 
> Luke
> 
> ----------------------------------------------------------------------------
> Luke Bakken				lbakken@ics-server.interface-net.com
>         m/(Net Admin)|(Equipment Manager)|(Bassoonist)|(UNIX hacker)/
> ----------------------------------------------------------------------------
> 
> On Tue, 28 Mar 2000, Marco S Hyman wrote:
> 
> > 1) cd /usr/src/lib/libssl
> > 2) rm -rf obj/*			# skipping this step will break things
> > 3) make -f Makefile.bsd-wrapper obj
> > 4) make -f Makefile.bsd-wrapper
> > 5) sudo make -f Makefile.bsd-wrapper install
> > 
> > This will install the standard lib versions.  Then, depending upon
> > your location (USA or other) grab /usr/ports/security/ssl26
> > or ftp://ftp.snafu.org/pub/sslUSA-port.tar.gz and build and install
> > the RSA enabled package.
> > 
> > // marc
> > 
> 

-- 
Todd Fries .. todd@fries.net