RE: Thread safe callbacks never actually called

2013-08-15 Thread Ludwig O'Hallorans
PM To: openssl-users@openssl.org Subject: RE: Thread safe callbacks never actually called A crash in crypto_free most likely means that some code outside the OpenSSL library has corrupted the heap, perhaps by freeing an area more than once or simply scribbling over its control data. One of the usu

RE: Thread safe callbacks never actually called

2013-08-15 Thread Jeremy Farrell
A crash in crypto_free most likely means that some code outside the OpenSSL library has corrupted the heap, perhaps by freeing an area more than once or simply scribbling over its control data. One of the usual memory allocation debugging tools should be able to help you pin down the guilty part

RE: Thread safe callbacks never actually called

2013-08-15 Thread Salz, Rich
> I don't mean the type, I mean the data By putting EVERYTHING with __declspec(thread)? That's not right either, as it completely prevents sharing. And the Windows DLL malloc model isn't the same Unix/Linux. Enough pedanticism. Most objects aren't safe to be used by multiple threads at the

RE: Thread safe callbacks never actually called

2013-08-15 Thread Ludwig O'Hallorans
-Original Message- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Salz, Rich Sent: Thursday, August 15, 2013 2:39 PM To: openssl-users@openssl.org Subject: RE: Thread safe callbacks never actually called > There should be a way. There i

RE: Thread safe callbacks never actually called

2013-08-15 Thread Salz, Rich
> There should be a way. There isn't. > There are syncronization method to keep the same structure used by many > threads at the same time, and ussually this is transaparent to developers. Are you new to multi-threaded C programming? -- Principal Security Engineer Akamai Technology Cambridg

RE: Thread safe callbacks never actually called

2013-08-15 Thread Ludwig O'Hallorans
] On Behalf Of Salz, Rich Sent: Thursday, August 15, 2013 2:24 PM To: openssl-users@openssl.org Subject: RE: Thread safe callbacks never actually called > But I think the structures should be thread safe as the functions Then where and how do you propose to store the state of any ongoing com

RE: Thread safe callbacks never actually called

2013-08-15 Thread Salz, Rich
> But I think the structures should be thread safe as the functions Then where and how do you propose to store the state of any ongoing computation? -- Principal Security Engineer Akamai Technology Cambridge, MA __ OpenSSL Pro

RE: Thread safe callbacks never actually called

2013-08-15 Thread Ludwig O'Hallorans
enson Sent: Thursday, August 15, 2013 12:15 PM To: openssl-users@openssl.org Subject: Re: Thread safe callbacks never actually called On Tue, Aug 13, 2013, Joshua Miller wrote: > Hello OpenSSL, > > I am attempting to encrypt a data stream with multiple threads calling > EVP_CipherU

Re: Thread safe callbacks never actually called

2013-08-15 Thread Dr. Stephen Henson
On Tue, Aug 13, 2013, Joshua Miller wrote: > Hello OpenSSL, > > I am attempting to encrypt a data stream with multiple threads calling > EVP_CipherUpdate. I have set the thread_id and call_back functions as > defined by the API. These functions are never being called, however. I've > used CRYP

RE: Thread safe callbacks never actually called

2013-08-15 Thread Ludwig O'Hallorans
Hi: I'm using CSMTP code, witch is based on OpenSSL, to send email from our software to SMTP servers. And everything works fine if the concurrency is low but as soon ad more than 3 thread start sending at the same time, after a while the module crash and for what I see it has something to do wi