Hi All,
I'm using Apache 1.3.31 with mod_ssl 2.8.17 and
OpenSSL 0.9.7d binaries. I use RSA based self signed
certificates for SSL communication.
My httpd.conf has the following SSLCipherSuite
configured
SSLSessionCacheTimeout 600
SSLOptions +StdEnvVars +ExportCertData
SSLCipherSuite
ALL:!ADH:!E
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Tim Rice
>Sent: Monday, May 30, 2005 10:19 PM
>To: openssl-dev@openssl.org
>Subject: When do we stop supporting old platforms?
>
>
>
>I notice my OpenServer 3 box will not compile the 0.9.8 betas.
>...
>[EMA
I notice my OpenServer 3 box will not compile the 0.9.8 betas.
...
[EMAIL PROTECTED] 13% make
making all in crypto...
sh[2]: 13003 Memory fault(coredump)
*** Error code 1
[EMAIL PROTECTED] 14% gmake
making all in crypto...
gmake[1]: Entering directory `/usr/local/src/libs/openssl-0.9.8/crypto'
(
I'm looking into http://gcc.gnu.org/PR19923
which claims that gcc-4.0 is slower on 'openssl speed'
than earlier versions. The only huge regression seems
to be in md2. Has anyone else looked at this yet?
I imagine it's a gcc problem, but I thought I'd ask
here just in case.
OpenSSL 0.9.7e 25 Oct
OpenSSL_0_9_8-stable branch pulled Mon May 30 19:47:25 PDT 2005.
On my unixware-7 boxes configured with the shared & no-sse2 options
i'm getting this error.
LIBDEPS=" $LIBRARIES -lsocket -lnsl" \
link_app.${shlib_target}
Undefined first
On Sat, 21 May 2005, Tim Rice wrote:
It looks like SHA512 requires a 64bit data type.
So on older platforms that do not have long long support,
you get errors like
making all in crypto/sha...
gmake[2]: Entering directory `/var/local/src/libs/openssl-0.9.8/crypto/sha'
cc -I.. -I../.. -I../.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 0.9.8 Beta 3
OpenSSL - The Open Source toolkit for SSL/TLS
http://www.openssl.org/
OpenSSL is currently in a release cycle. The third beta is now
released. The beta release is available for
However during compilation I get warning about size_t to
int and long conversations: possible loss of data. This is because
size_t and even SOCKET is 64 bit wide in this environment.
Should I care about this?
Not about SOCKET, because even though it's declared a pointer-type, it's
safe to cas
Hi!
I have successfully compiled OpenSSL 0.9.8-beta2 using the new platform SDK
which
includes 64 bit compiler for AMD 64 and EM64T processors on windows x64.
After the compile the tests are successful and even my 64 bit applications
worked properly and fast :)) (Of course I had to use do_ms
On May 29 15:35, Geoff Thorpe wrote:
> Corinna, Richard,
>
> I've commited changes to HEAD and the 0.9.8-stable branches, please let me
> know if you see any problems.
I tried CVS HEAD and this looks good to me, as far as I can test it.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Project Co-L
How can I submit a
potential bug in SSLeay32.dll and/or libeay32.dll.
Thank
you.
11 matches
Mail list logo