This is the problem I'm have with Windows XP. Now it CAN be fixed by regenerating a cert until one works with XP but this is such a hastle as I have to do a web machine at least once a week. But this is what I get when I have a cert that doesn't like to work with XP. I know they released a so called patch here. http://support.microsoft.com/default.aspx?scid=kb;EN-US;q314864 . This is what I get in the log ssl_engine_log.
[10/Apr/2002 13:53:16 21206] [info] Connection to child 0 established (server www.yahoo.com:443, client 0.0.0.0) [10/Apr/2002 13:53:16 21206] [info] Seeding PRNG with 1160 bytes of entropy [10/Apr/2002 13:53:16 21206] [info] Connection: Client IP: 0.0.0.0, Protocol: SSLv2, Cipher: RC4-MD5 (128/128 bits) [10/Apr/2002 13:53:16 21206] [info] Connection to child 0 closed with standard shutdown (server www.yahoo.com:443, client 0.0.0.0) As you can see the connection from the browser terminates immediatly after the encryption has been determined. This happens for 512/1024/2048 etc etc etc. I've found no consistancy. At least with what I can see. Does anyone know whats going on here? Jeremy Walton DICE Corporation ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]