Greetings,
Lots of you have said you'd be interested in the results [of my experiences
with RSA BSAFE SSL-C], so unless anyone objects I'll post them here and on
the ssl-users list. Eventually they'll make way onto my website.
However, I may not get very far because one thing I _can_ say is
Jon Parry-McCulloch wrote:
Greetings,
My company has just bought RSA BSAFE SSL C for me to use in the
exported-to-the-US versions of the product we're developing.
Two things:
a) anyone know if this is call-for-call compatible with SSLeay 0.9b
not
rsa won't be too pleased
i'd check the licience
You think the licence contains stuff that stops me from saying "it
was easy to use and it worked a treat" or "it was hard to use and I couldn't
get it to do anything?".
I doubt that. Isn't RSA an
I'm going to delay applying this patch; after applying some connections
fail:
try openssl -connect www.trustcenter.de:443 [fails]
try openssl -connect www.trustcenter.de:443 -no_tls1 [passes]
On Sun, 31 Jan 1999, Mark J Cox wrote:
In going through our internal code I came across some changes
Mark J Cox wrote:
I'm going to delay applying this patch; after applying some connections
fail:
try openssl -connect www.trustcenter.de:443 [fails]
try openssl -connect www.trustcenter.de:443 -no_tls1 [passes]
Hmmm ... do we know what they run? Could it be an old version of SSLeay
that
You can use all the d2i_xxx and i2d_xxx to perform
DER decoding/encoding of ASN1 objects. The i2d
stands for internal (C structures) to DER form.
For example, i2d_X509() DER-encode a X509 certificate.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
