> 3. Has anyone tried RSA product called "SSL-C", which is a set of object
> libraries for developing software using the SSL protocol or has anyone tried
> the SSLPlus?
I got an eval. It's an enhanced version of SSLeay with some of the API
entry points hidden. The enhancements are many, mostly things that Tim
& Eric had already added to SSLeay but hadn't released.
> 4. I heard that RSA appears to be taking a hard-line stance on OpenSSL's use
> of their technology, and they apparently will not license the use of their
> crypto technology within OpenSSL at all. Any enlightenment to this issue?
I don't know about hard-line. There was a time when RSA had no SSL toolkit,
and they would talk to you about patent licensing even if you didn't want
to buy BSAFE. It was difficult even then to get put through from the sales
guy to the people who can license the IP directly, though I suspect that if
you have a good enough reason (where good enough is measured in $) you can
still do it. Be prepared for "good enough" to reach or exceed six digits
though, after royalties. Major products only, folk.
We simply decided that in the USA, we should use standard MS things until
next September, when the oppressed US populace can use our international
versions. RSA have a definitive Y2K problem :-)
------------------------------------------------------------
Clifford Heath http://www.osa.com.au/~cjh
Open Software Associates Limited mailto:[EMAIL PROTECTED]
29 Ringwood Street / PO Box 4414 Phone +613 9871 1694
Ringwood VIC 3134 AUSTRALIA Fax +613 9871 1711
------------------------------------------------------------
Proven Solution Deployment for the Global Enterprise
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
