>
> The timing on this is amusing. A full five months after they
> announced SSL-C, with a BSAFE API. I wonder how they got the BSAFE API
> legally exported to Australia. hm.
>
I suspect reverse engineered from the hooks in the exportale SET
reference implementation. There is a glue-on interface availale quite
some time before SSL-C from a third party oversea source replacing
BSAFE with SSLeay for SET. IIRC it was from a Stronghold server :)
David Chia, RMIT University
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
