We are doing some OpenSSL programming, and I came across this thread. It sounds like the multi-thread restrictions are mostly around renegotiation. My question is "if renegotiation never happens, can you have a reader thread and a writer thread active simultaneously?". We control both endpoints, so it would be nice to not worry about this in the case where we never renegotiate. Thanks, --john
JoelKatz wrote: > > Ofer Avitzur wrote: > > OpenSSL is fine with reads coming from one thread and writes coming from > another, so long as all operations are non-blocking and you don't do a > read > and a write on the same SSL connection at the same time[...] > The classic failure case is this one: > 1) A renegotiation is in progress... > [...] > -- View this message in context: http://old.nabble.com/Calling-SSL_read-write-in-client-application-tp27511645p34483804.html Sent from the OpenSSL - Dev mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
