In article <[EMAIL PROTECTED]>, David Woolley
<[EMAIL PROTECTED]> wrote:
> Hello.
>
> Earlier this year, I reported difficulty logging onto my online bank. Holger
> reported that it would be possible with MiamiSSL v2.
I said no such thing. I said that MiamiSSL v2 will have support for
SSL v3 and TLS v1, which is what SOME banks and other servers may
require, but that does not mean that just because of all MiamiSSL v2
all of the various web incompatibilities between PCs and Amigas will
suddenly magically disappear.
If online banking does not work for you then you need to find out
WHY that is. It COULD be because of an obselete SSL version. In
that case try MiamiSSL v2. It could also because of explicit browser
name checks (try spoofing), JavaScript, Java, incompatibilities in
cookies, problems with SSL through proxies or a number of other reasons.
> Unfortunately, I've just installed the new MiamiSSLv2, and it doesn't seem to
> make any difference.
>
> http://www.fastnet.helios.co.nz/cgi-bin/fastnet/fastnet.pl This is the log-in
> page, which includes a demo. Ibrowse 1.22 can handle the demo, but Voyager
> 2.95 using MiamiSSL v2 can't- when I try it simply comes up with the login
> page again.
Looks like a problem with the way Voyager handles POST in forms. Actually
that login page does not use SSL at all. It uses normal, unencrypted
insecure transmissions, and the problem has nothing to do with SSL.
> http://www.asbbank.co.nz/about-fastnet/application.stm
That's a case of server stupidity. The server only supports requests
that have the obsolete SSL v3 version identifier, as MSIE and NS sends
them, but not requests with the TLS v1 version identifier, the official
Internet standard. Both of them only differ in the revision number.
Making matters worse, the automatic fallback from TLS v1 to SSL v3,
which is supposed to make this difference transparent, and which all
v3 servers are required to implement, is not working here. The server
simply disconnects when it gets a TLS request, instead of falling
back to SSL v3.
In the next version I'll add an option to let MiamiSSL explicitly
retry in SSL v3 if the server hangs up with TLS. Sigh... In the meantime
you may want to contact the back and let them know about this. With the
next version of MSIE or NS their server will probably break as well.
Everyone is starting to implement TLS these days...
--
Holger Kruse [EMAIL PROTECTED]
http://www.nordicglobal.com
NO COMMERCIAL SOLICITATION !
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
