[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: identical input, different output?
On 12/05/14 13:41, Arnold Reinhold wrote:
>> On Dec 5, 2014, at 3:24 PM, Colin Percival <email@example.com> wrote:
>> On 12/05/14 07:59, firstname.lastname@example.org wrote:
>>>> Which version of the scrypt code are you using? If you're using the SSE2
>>>> version, are you sure that you're running on an SSE2-enabled CPU?
>>> Do you mean to say that if you run the crypto_scrypt-sse.c function on a
>>> non-SSE CPU, you will get a different result than on a SSE CPU?
>> My understanding is that some non-SSE CPUs treat SSE instructions as NOPs.
> If so a quick trial SSE calculation would reveal the absence, allowing an error return. Seems prudent.
Yes, I'm planning on adding code to do that. But I don't know if that's the
issue which Maarten ran into.
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid