[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANO7a6wM4CnSRyBdWVeLDxSbub8FvR8QyUwjLgiTg2NDhKhz=Q@mail.gmail.com>
Date: Fri, 16 Mar 2012 21:33:40 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: SSH thread-safety
On Fri, Mar 16, 2012 at 8:36 AM, Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Fri, Mar 16, 2012 at 5:16 AM, Solar Designer <solar@...nwall.com> wrote:
>> It was reported to me off-list that the "SSH" format in 1.7.9-jumbo-5
>> crashes on self-test on a 64-way machine running RHEL 6.2 on x86-64.
>>
>> I managed to reproduce similar crashes on an 8-core machine by
>> increasing OMP_NUM_THREADS:
>>
>> My guess is that the OpenSSL functions we're calling are still not
>> entirely thread-safe even in these recent versions of OpenSSL. We could
>> want to look into this and maybe end up submitting a patch to OpenSSL.
>
> Will using crypto_set_locking_callback function solve these problems?
>
> http://www.openssl.org/support/faq.html#PROG1
> http://linux.die.net/man/3/crypto_set_locking_callback
I have implemented the callbacks required and segfaults are gone. Can
you give the new code a shot? Thanks!
--
Cheers,
Dhiru
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
