On Wed, May 12, 2004, Richard Holliday wrote: > Thanks very much for your comments. > > I agree that if the MS software was causing this issue it would manifest > itself with a direct con. as well. > > The version numbers I get when routing through a proxy are major = 0x0054 > and minor = 0x0054. These are being compared against the SSL* s version > which is 0x0300. > > These are consistent each time I use the proxy connection. Direct > connections match to 0x0300. > > I'll take a look at disabling the TLS this morning and also installing a > newer proxy server. >
Well the cause isn't a broken SSL/TLS implementation: it is something else. >From those values it looks like the version number is garbage and may be being corrupted through the proxy or some other cause such as some added proxy headers. What does the connection look like when you issue the CONNECT command using something like telnet? Do you get connected straight away or does some message come back from the proxy? If you do get some message from the proxy you'll need to swallow that before attempting the SSL connection. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Funding needed! Details on homepage. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
