On 12-Apr-99, Holger Kruse wrote:
> AFAIK SGC is just a set of checks that disables 128-bit encryption
> support in the browser in situations where a server does not have
> a certain type of certificate (or put the other way around:
> SGC-compliant server certificates cause the export versions of
> some PC browsers to enable their existing, but usually dormant,
> 128-bit support.)
>
> This really only affects PC browsers which have crippled 128-bit
> support for export. All Amiga SSL implementations (including
> VoyagerSSL, IBrowseSSL and MiamiSSL) have FULL strength encryption
> (up to 168-bits, including 128-bit support) ALL THE TIME,
> regardless of whether the server certificate is SGC-compliant
> or not, so they always allow 128-bit encryption, with fortified
> servers and with SGC servers.
>
Well, Voyager gave
Unable to open document
https://easibank.countrywide.co.nz/cgi-bin/check128ssl.dll
SSL handshake failed
and IBrowse
SSL Connect Error. The remove server is using a protocol not supported by
IBrowse.
I'm not sure if MiamiSSL deals with it as I have never delved into setting
up V to use it and I have never successfully got IBrowse to use it.
If any one wants to have a look the bank is at
http://countrywide.co.nz
on the internet banking page there is a check encryption link to the URL in
the V error return.
Any ideas gratefully accepted
regards
Mike Butler
