[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d864c2751aebbce2700029357f0cd031@smtp.hushmail.com>
Date: Mon, 31 Dec 2012 07:04:07 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: New self-test for maximum length
On 31 Dec, 2012, at 4:48 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Monday 31 December 2012 02:14 AM, magnum wrote:
>> On 30 Dec, 2012, at 18:11 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
>>> On Sunday 30 December 2012 10:26 PM, magnum wrote:
>>>> Benchmarking: Clipperz SRP SHA256 [32/64 oSSL-exp]... (8xOMP) FAILED (get_hash[0](6))
>>>>
>>> I will look into this one tomorrow.
>> I had a look at it but saw nothing. It's intermittent, works once out of about four with OMP build, but no problems seen with non-OMP. Very trivial code, I really can't see what could be wrong with it.
>> ilf
>> Apart from that one, the dynamics are the only ones left that I know of (and I just heard from Jim, he's on it!). We've nailed quite a few bugs the last couple of days 8^)
>>
>
> 1. Are we using non-thread safe OpenSSL functions in this format? OpenSSL could be breaking OMP builds (just guessing).
That's it, commenting out the OMP pragma fixes the problem.
> 2. This format is a copy of wow_srp format. There isn't much difference between them. So why doesn't wow_srp format exhibit
> similar problems?
Jolly good question. It's nearly identical but wowsrp use SHA1 and clipperz use sha256. I just ran wow like 30 times in a row with no problem. Maybe SHA256 is not thread-safe. With that interface, you'd think it should be :-/
magnum
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.
