On Wed, 19 Apr 2000, Holger Kruse wrote:
> MiamiSSL version 2.21 is available for download from www.nordicglobal.com
> now. Changes since 2.11:
>
> - The "infinite garbage bug" which caused MiamiSSLClient to loop
> after displaying common SSLv2 ciphers is fixed.
Yes, at least one case that used to fail now works.
> - Some expired certificates have been replaced with newer versions.
Unfortunately that still isn't making WellsFargo happy. I'm not sure
exactly what it's checking, but the certificate references I see with
SnoopDOS are for "cert.pem" (6 Opens) and "v2certs/f73e89fd.0" (3 Locks,
then 3 Opens). There are also some unsuccessful probes of
"v2certs/f73e89fd.1" (3 Locks); checking for hash collisions, perhaps?
The problematic URL is:
https://banking.wellsfargo.com/
Is it possible that WF requires a client-side certificate, and doesn't
like the NordicGlobal one? If so, could one swipe a certificate from
Netscape or IE?
Is there a way to display the contents of a certificate file in a more
readable form (e.g. to see what f73e89fd.0 really is)? I have an old port
of SSLeay (0.8.1b) that might work for this if the feature doesn't exist
in MiamiSSLClient. I believe the hashes are incompatible, but that might
not matter for this purpose.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
