Hi
I am getting the following error when trying to connect to
stream-api.betfair.com:443
Error connecting with SSL.
error:1408E098:SSL routines:SSL3_GET_MESSAGE:excessive message size
using OpenSSL. However using code I wrote using SChannel it works fine.
I looked around and it looks like
The HOST_c2l() macro assigns the value to the specified variable, but also
evaluates to the same value. Which we ignore, triggering a warning.
To fix this, just cast it to void — like we did in commit 08e553644
("Fix some clang warnings.") for a bunch of other instances.
---
There seems to be a bug in the AVX2 codepath in poly1305-x86.pl. I have not
attempted to debug this, but I have attached a test file which produces
different output in normal and AVX2 codepaths. Our existing poly1305
implementation agrees with the former.
$ OPENSSL_ia32cap=0 ./poly1305_test
PASS
closed with commit 104ce8a thanks.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4116
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
With the following patch,
% ./Configure --unified solaris-x86-cc
% make
% make test
passed.
% ./Configure --unifiedsolaris64-x86_64-cc; make; make test
also passed.
This patch was written comparing to openssl-1.0.2f.
It has side effect for other configurations.
Please add some conditions.
The first parts of this report are the actual build bug I think I am
encountering, but also, at the end, I am asking for additional help with
enabling the crypto-mdebug and crypto-mdebug-backtrace as I am trying to
to diagnose a compatibility issue between tor and the openssl 1.1.0_dev
branch.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release of
OpenSSL versions 1.0.2g, 1.0.1s.
These releases will be made available on 1st March 2016 between approximately
On 24/02/16 15:50, The Doctor wrote:
> As of 2106-20-24 SSL_librbary_init may not be avialable in the libssl.so .
>
> Is their a workaround for this?
>
SSL_library_init is still available in ssl.h as a compatibility macro:
#if OPENSSL_API_COMPAT < 0x1010L
# define SSL_library_init()
