I've been trying to integrate Netscapes iPlanet Web server and a NSAPI
application. This NSAPI client application uses openSSL to connect to a
backend server.
I've run into some symbol clashes with openssl v.0.9.5 and linking
with the iPlanet Web Server. Below is a partial list of symbols from
Hi Andrew,
Normally I'd just reply to this on the openssl-users list, but this may
actually be of interest (or at least mildly amusing) to OpenSSL developers
too ...
On Wed, 18 Oct 2000, Andrew Rickard wrote:
[snip]
I've run into some symbol clashes with openssl v.0.9.5 and linking
with
Dr S N Henson wrote:
I make the verification using a call to X509_verify_cert.
When the call returns, they are some errors left in the error stack from
a call to check_issued to check if the check is self-signed or not.
Is this a normal behaviour ?
That shouldn't happen unless you
Richard Levitte - VMS Whacker wrote:
Actually, that macro mumbo-jumbo should be avoided and we should adopt
a new name standard, but that will also require a lot of work, not
only on our part... Perhaps to version 1?
Or dump the low level APIs...
geoff Thoughts anyone?
Well, apart
Based on the change:
from:
openssl-0.9.5/crypto/crypto.h
#define Free(addr) CRYPTO_free(addr)
to:
openssl-0.9.6/crypto/crypto.h
#define OPENSSL_free(addr) CRYPTO_free(addr)
the following instances of Free calls in openssl-0.9.6/demos/ssl should
be
Gentlemen,
While testing OpenSSL functionality with a client
and serverapp I wrote,
I encountered the
following issue:
If the server code is using the SSL_METHOD
SSLv3_server_method and the client
is using TLSv1_client_method, the server fails
tonegotiate connection. This does
not happen
