> John Castillo wrote:
> built SSLeay0.8.1b
Why are you're using this old version. Upgrade to latest OpenSSL release
from http://www.openssl.org/ .
> Jul 15 17:45:20 phoenix stunnel[12524]: Wrong permissions on
> /usr/local/ssl/certs/stunnel.pem
Since the file stunnel.pem contains a private ke
John,
Looks like you use the old certificate (stunnel.pem)
with the new stunnel. The DH errors mean you won't
be able to use DH algorithm for key exchange.
RSA will work for you, anyway.
Solution: Do "make cert" and install the new certificate.
About permissions: Certificate should be only r
Kwon JaeHwan wrote:
>
> Thank U for the information.
>
> I've found the related articles whose title was "creating a subset of openssl" and
>
> "Howto make a small footprint lib?".
>
> By the way, in those articles, what's the meaning of the following sentences?
>
> "On a side note: Disabling
Hello
I myself was very excited when I found this documentation of SSLEAY.
Perhaps you don't know about this site:
http://www.mikom.csir.co.za/SSLeay/
have a look.
Tom
The bio explantion is just beatiful.. Snif..
http://www.mikom.csir.co.za/SSLeay/bio_struct.html
_
>All endianness problems should be handled by ntoh... and
>hton... macros/functions. I have never checked whether everything is
>really done right, but if handled correctly, things like that don't
>cause problems.
Is OpenSSL running on any big-endian machines? (Uh oh-- I always get
that wrong.
I'm trying to get OpenSSL working on a Mac (yeah, yeah-- I know), but
have run into some problems, and I'm hoping for some advice. And yes,
I've searched the mailing list archives before posting this. :-)
Anyway, the big problem is that the Mac doesn't support sockets. There
is a nice sock
The OpenSSL core team is proud to announce that
Andy Polyakov <[EMAIL PROTECTED]>
(now aka <[EMAIL PROTECTED]>) has joined the OpenSSL development team. From
the past we already know Andy as a great OpenSSL contributor and with his new
received status inside the OpenSSL project we're su
