On 11/24/04 02:19 PM, Louis LeBlanc sat at the `puter and typed: > > <SNIP> > > Have you tried connecting using s_client? I suggest you try it with > > -bugs and possibly also restricting the ciphersuites in use too and > > possibly the SSL protocols too. > > Now that sheds a little light. It comes through fine even without the > -bugs parameter, so it looks like my app isn't handling something > right. > > Is there something I can do prior to the SSL_read() to verify that > it's set up correctly? > > In the meantime, I'll run back to the client code and get it to > reproduce the behavior with the s_server feature. Perhaps it will be > a little more verbose than the server.
Wouldn't it be nice if my client were having the same problem with the s_server tool. No such luck. Here's the rundown: My client cannot successfully fetch from a particular secure server. The OpenSSL s_client tool can. My client has no problem fetching from any other secure servers, including the OpenSSL s_server tool. My client establishes the connection (socket, then SSL handshake) and sends its request headers, then gets an EOF when trying to read the response - on the very first read. I believe the server is IBM Websphere. This is a customer server, and they have assured us their logs don't indicate we ever connected - our access to this server is pretty much nonexistent. Any other ideas would be welcome. Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Don't go around saying the world owes you a living. The world owes you nothing. It was here first. -- Mark Twain ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
