any help is appreciated.
----
Sankaran Narayanan http://www.cs.columbia.edu/~sankaran
__
OpenSSL Project http://www.openssl.org
Us
> I am afraid that SSL_dup() does not fulfill your requirements.
> You can only have one datastream through one SSL object at a time,
> so that you cannot have two threads concurrently accessing one SSL object.
Thanks. It was fairly trivial to write a "reference counted" wrapper object
for SSL*,
> Out of curiosity, doesn't one also have to lock the SSL* itself against
> concurrent access during read/write operations, or does OpenSSL guard it
> for the programmer?
sorry if i am spamming with naive questions, but:
Do i need locking, if all i do is 'read' in one thread (from remote) and
'
...i suppose right now openssl does not natively provide support
for IPv6...is there a plan to add one? or, if i want to enable IPv6
support - is writing a BIO the correct thing to do?
comments appreciated.
---
Sankaran Narayanan
i have tried:
http://members.netscapeonline.co.uk/jeremyalansmith/ssltutorial/
http://www-itg.lbl.gov/~boverhof/openssl_certs.html
and found them quite helpful.
---
Sankaran Narayanan http://www.cs.columbia.edu
