Greetings... Fred
On 21-Apr-00, Fred Wright wrote:
> On Wed, 19 Apr 2000, Holger Kruse wrote:
[snip]
>> - 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?
Actually, I don't believe that the check actually checks for certificates
at all. I believe it still just does the old "check the browser version"
check. I have an account with Wells Fargo and did use to see the "You
need to upgrade your browser by May 5, 2000" screen. All it took in my
case was upgrading Voyager to version 3.1. I am not using Voyager's SSL.
And I upgraded to Miami 2.21 afterwards but it has not changed a thing.
Try Voyager to see what I mean.
> 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?
I don't believe so.
[snip]
Fare thee well,
Carlos A. Tirado
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
