>From www.e-softinc.com/probe/probe.html:
Site being probed: https://banking.wellsfargo.com:443
Web Server: Netscape-Enterprise/3.6 SP2
Operating System:
nmap's best guess: Digital UNIX OSF1 V 4.0,4.0B,4.0D
Queso's best guess: Berkeley: usually Digital Unix, OSF/1 V3.0,
HP-UX 10.x
Bodo Moeller wrote:
>
> Mixmaster <[EMAIL PROTECTED]>:
> > [EMAIL PROTECTED] (Bodo Moeller):
>
> [...]
> >> openssl s_client -ssl2 -bugs -connect banking.wellsfargo.com:443
> >> should work. Look in the s_client source to see what exactly this does
> >> (it sets all the bug workaround options).
>
> > It would be nice if "support" for these newer buggy servers was added to
> > to set of built in workarounds covered by -bugs. Then apps could just
> > enable the workarounds and go, without dropping back to the lowest common
> > denominator (SSL2) to guarantee interoperability.
>
> Does that server ("Netscape-Commerce/1.12" last I checked) support
> anything but SSL 2?!
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
--
------------------------------------------------------------
Thomas Reinke Tel: (416) 460-7021
Director of Technology Fax: (416) 598-2319
E-Soft Inc. http://www.e-softinc.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
