>From: Sameer Parekh
>To: [EMAIL PROTECTED]
>Subject: Re: BSAFE API published
>Date: 1999-05-14 02:07
>
>---------------------------------------------------------------------------
---
>
> 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.
This isn't a problem - after all it is still within the company, albeit an
Australian
subsidiary!!
As far as getting hoild of the BSAFE API -- I managed to get hodl of the
BSAFE
version3.0 Library Reference Manual and User's Manual via a purchase over
the net. Unfortunately, I had to pay more for the international courier to
deliver them
to Australia than the manuals themselves [post was not a delivery option!].
Roland SEIDL
Telstra Research
>
>> Ulf M�ller wrote:
>> >
>> > RSA has published the BSAFE API as an Internet draft.
>>
>> I wonder why?
>>
>> > http://www.ietf.org/internet-drafts/draft-baldwin-bsafe-00.txt
>>
>> Well, that's a bit dozy, isn't it? They call it "BSAFE CRYPTOGRAPHIC
>> SECURITY COMPONENTS" and then they say:
>>
>> BSAFE and JSAFE are trademarks of RSA Data Security, Inc.
>>
>> which, presumably, means they'll (try to) prevent anyone from using
>> them, rather as they do with RC4. Duh!
>>
>> BTW, is there a mailing list for discussion of this?
>>
>> Cheers,
>>
>> Ben.
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
