Re: BIO_new_CMS with CMS_DETACHED

On Wed, Oct 01, 2014, Pedro Lamaro wrote: > Hello, fellows. > > I am implementing a new streamer for CMS_SignedData with CMS_sign. > Because I need to adapt a certain input and output interface, I chose > to use BIO pairs with BIO_new_CMS. I read from my original input > stream, write into the CM

Re: Thread Safety of ssl_write()

Hi, It is unsafe to access SSL context from 2 different threads. When you call SSL_write function, the SSL context object state is changed. Probably you can end up in case that data is not delivered to the peer. Kris On Tue, 2014-09-30 at 13:46 +, S P, Swaroop (NSN - IN/Bangalore) wrote: > H

BIO_new_CMS with CMS_DETACHED

Hello, fellows. I am implementing a new streamer for CMS_SignedData with CMS_sign. Because I need to adapt a certain input and output interface, I chose to use BIO pairs with BIO_new_CMS. I read from my original input stream, write into the CMS filter, read from the pair and write to the original

RE: Thread Safety of ssl_write()

[Top-posted because Outlook can't deal correctly with HTML email.] > Is this safe? No. There's a lot of state in the SSL object (which is not an "SSL context", in OpenSSL terminology; the SSL_CTX object is an "SSL context"), and the SSL/TLS methods' write functions do not serialize access to it

Issue linking FIPS with OpenSSL libraries

Hi All, Having two issues with OpenSSL with FIPS for ANDROID. Issue 1: I am compiling OpenSSL-1.0.1i with OpenSSLFips-2.0.7 under MIPS EL architecture for FIPS support for ANDROID. And when I crossed compile for using the 'fips shared' config option, I still get a static libs (libcrypto.a & libssl

Thread Safety of ssl_write()

Hi, We have a use-case where multiple threads are required to use the same SSL context [created using SSL_new()] and do a ssl_write(). So, there might be a scenario where two threads (or more) can be doing a ssl_write() on the same SSL context at exactly the same time. Is this safe? Is the data