SSL_get_error() returns 1 and ERR_error_string( ERR_get_error() )
returns "error::lib(0):func(0):reason(0)".
__
OpenSSL Project http://www.openssl.org
User Support Mailing List
I'm curious: what does SSL_get_last_error give? What stack does
ERR_get_error give?
-Kyle H
On Tue, Jul 29, 2008 at 11:36 AM, Alen Puzic <[EMAIL PROTECTED]> wrote:
> We are using dynamic linking - using dlopen to open the shared objects
> and then load the function symbols we are using. All the
We are using dynamic linking - using dlopen to open the shared objects
and then load the function symbols we are using. All the symbols load
correctly and I haven't seen any function calls causing any crashes
yet. I just get an SSL_connect() error on the client end which results
in error SSL_ERROR_
On Mon, Jul 28, 2008 at 09:39:04AM -0400, Kenneth Goldman wrote:
> In my experience, openssl releases routinely break compatibility.
> This occurs for letter as well as number changes.
>
> Compiling against the new version is not enough. You must
> link with the same version. Dynamic linking of
In my experience, openssl releases routinely break compatibility.
This occurs for letter as well as number changes.
Compiling against the new version is not enough. You must
link with the same version. Dynamic linking offers a
third possibility for inconsistency.
The symptom I typically see is
Hi everybody,
I'm working a project that uses OpenSSL to securely communicate
between server and client. So far the project has been using OpenSSL
version 0.9.7l but last week we decided to switch to 0.9.8.f. Our code
compiled against the new version just fine but now it no
longer works properly.
