Wed Jun 5 13:00:00 CEST 2002
I have had OK experience using openssl with this www.openssl.org
Create the two library files libcrypto.a and libssl.a using the openssl
standard build procedure
Copy them into the lib/ssl-x.y.z/priv/bin directory
Adjust the paths in the Makefile referred to in the documentation
Give it a go
> -----Original Message-----
> From: Peter H|gfeldt [mailto:]
> Sent: 05 June 2002 11:22
> To: Yurii Rashkovskii
> Subject: RE: ssl_esock.exe
> To provide an interface in Erlang to SSLeay and to ask users to aquire
> the SSLeay package themselves, is a device that we have found
> to fulfil
> both the restrictions put on cryptographic software by the legislation
> of the European Union, and the requirements in the SSLeay license.
> So I am sorry, as an Ericsson employee, I dare not help you with this
> matter, due to the quagmire of legal restrictions.
> On Wed, 5 Jun 2002, Yurii Rashkovskii wrote:
> > I know about it.
> > Bu as how it is said in documentation the process is not
> trivial and may
> > have problems. I'm very limited in time (*very*!), and it
> will be very
> > good if someone will send me already built ssl_esock.exe :)
> > -----Original Message-----
> > From: Peter H|gfeldt [mailto:]
> > Sent: Wednesday, June 05, 2002 12:55 PM
> > To: Yurii Rashkovskii
> > Cc:
> > Subject: Re: ssl_esock.exe
> > There are instructions on how to build ssl_esock.exe in the SSL
> > application manual page (man -s 6 ssl). You have to download the
> > SSLeay package.
> > /Peter
> > -
> > Peter Högfeldt e-mail :
> > Open Telecom Platform Phone: : +46 (8) 727 57 58
> > Ericsson AB
> > >
> > > I've found that there is no ssl_esock.exe in my Windows
> > of
> > > Erlang/OTP R8B0.
> > >
> > > Where can I get it?
> > > (I've failed trying to build it from priv/obj/Makefile)
> > >
> > > P.S. It is very *urgent*.
> > >
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions