I haven't seen that, but I have seen Chrome (on MacOS 10.5.8) complain about the validity of certificates that don't bother Firefox. Paul
___________________________________ Paul A. Suhler | Firmware Engineer | Quantum Corporation | Office: 949.856.7748 | paul.suh...@quantum.com <mailto:paul.suh...@quantum.com> ___________________________________ Disregard the Quantum Corporation confidentiality notice below. The information contained in this transmission is not confidential. Permission is hereby explicitly granted to disclose, copy, and further distribute to any individuals or organizations, without restriction. ________________________________ From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Lou Picciano Sent: Friday, March 19, 2010 8:17 AM To: openssl-users@openssl.org Subject: Google Chrome certificate idiosyncrasies? Fellow OpenSSL-ers, We're beginning to look at an apparent discrepancy in the way Google Chrome (OS X) handles certificates. Though Chrome seems to use the same OS X-standard keychain application used by Safari, we are finding that Chrome reports the dreaded 'Handshake Re-negotiation' error in attempting to connect to certain locked-down websites, while Safari connects just fine. Hmm... More digging on this to follow. Meanwhile, anyone else run into this? Lou
