Hi,
I'm using openssl, (I think the slimmed
down engine version), and attempting to support a program written by someone
else. The server that I'm talking to recently moved to a new ISP and the
program stopped working. It should be as simple as getting the server's
new certificate and it should
Nils,
Yes, 0.9.6b is the exact version. Please
help!
Nils Larsch [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
08/26/2006 06:23 AM
Please respond to
openssl-users@openssl.org
To
openssl-users@openssl.org
cc
Subject
Re: Unable to locate the keystore/certificate
store or
Nils,
Yes. I read the entire e-mail. I can't
find ANYWHERE where it's being fed to the application, (including the source
code). As far as I can see, it's definitely not being used in an ssl_ library
call nor is he building his own in memory or using some other filename
etc. I don't see how the
The platform is AIX. I don't think they've
ever explicitly used a *.pem file. Somehow the app was able to communicate
with an IIS server and complete the handshake process or at least communicate
and get txn's across, (I'm not sure how).
Diffenderfer, Randy
[EMAIL PROTECTED]
Sent by:
The server side SSL is no longer terminated
on the IIS server. It is being handled by Cisco 11500 series content switches
and it the application will no longer work.
Diffenderfer, Randy
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
08/28/2006 03:23 PM
Please respond to
Excellent, excellent idea. Is ssldump
an API call? If so, I haven't seen that. Let me go out to the site
and look. I wish there were a more organized and informative source for
information on the openssl API.
That should definitely make the problem
expose itself. Thanks!
Marek Marcola
Nils,
The basic succession of calls are as
follows. I think the program waits for an ssl_read or ssl_write to implicitly
trigger the handshake process.
meth = TLSv1_client_method()
SSL_load_error_strings();
SSLeay_add_ssl_algorithms();
SSL_CTX_new(meth);
ssl = SSL_new( ctx );
sbio =
I will be out of the office starting 09/28/2006 and will not return until
09/30/2006.
If you require an immediate response, please contact me on my cell phone.
This message contains information from Equifax Inc. which may be
confidential and privileged. If you are not an intended recipient,
