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.
> 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.
>
> --
> http://www.apache-ssl.org/ben.html
>
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
> - Indira Gandhi
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> Development Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
--
sameer
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
