In article <[EMAIL PROTECTED]>, Michael Butler
<[EMAIL PROTECTED]> wrote:
> Hi Olli
>
> Any chance that V3 will support SGC encryption?
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.
This is true with all already existing Amiga SSL implementations,
and I don't see any reason why it would change with SSL V3 and
TLS -- which will also be supported in the upcoming MiamiSSL
release 2, btw, e.g. for Voyager users in the US who cannot use
VoyagerSSL for legal reasons.
--
Holger Kruse [EMAIL PROTECTED]
http://www.nordicglobal.com
NO COMMERCIAL SOLICITATION !
