Hi,
Thanks for replying.
The problem is that I already have a licensed copy of SSL-C, but now I find that
it does not have crypto support (for example ) to generate temporary RSA keys to be
used during
key exchange. I could code the DH params in the source file but not the RSA keys. So,
I just wanted
to know if RSA has split the openSSL package into 3 components SSL-C ,CERT-C and
CRYPTO-C
and whether I'd have to get a licnesed copy for CRYTO-C and CERT-C and whether they
are compatible
with SSL-C.
I have another doubt as well. Why are some certifcates branded as signing only?
I mean whats the difference between signing and encrypting (when both use some private
key)??
It might be pretty obvious, might really I fail to see it. If anybody could help me
with this, I'd be glad :)
Thanks,
Amit Chopra.
-----Original Message-----
From: Ulf Moller [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, December 04, 1999 2:16 PM
To: Amit Chopra
Cc: 'OpenSSL-Dev'
Subject: Re: RSA BSAFE kit Vs OpenSSL
> OpenSSL provides all crpyto stuff, cert stuff and SSL stuff packaged in one big
>package.
> But if I were using RSA SSL-C kit and I would have to crypto stuff like key
>generation
> would I need their Crypto-C kit too??
OpenSSL and BSAFE SSL-C both are derived from SSLeay. The most
important difference between the two is the price. ;-)
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
