[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: identical input, different output?

To: danielw@emaildoge.com, scrypt@tarsnap.com
Subject: Re: identical input, different output?
From: Colin Percival <cperciva@tarsnap.com>
Date: Fri, 05 Dec 2014 12:24:27 -0800
In-reply-to: <90a1f03fd091607c039a8c7e6133145e.squirrel@lelantoss7bcnwbv.onion>
References: <7AE9DD36-A667-4B8D-B2E1-FF781E28D995@lyndir.com> <54800408.8060905@tarsnap.com> <90a1f03fd091607c039a8c7e6133145e.squirrel@lelantoss7bcnwbv.onion>

On 12/05/14 07:59, danielw@emaildoge.com 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.

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid

Follow-Ups:
- Re: identical input, different output?
  - From: Solar Designer <solar@openwall.com>
- Re: identical input, different output?
  - From: Arnold Reinhold <agr@me.com>

References:
- identical input, different output?
  - From: Maarten Billemont <lhunath@lyndir.com>
- Re: identical input, different output?
  - From: Colin Percival <cperciva@tarsnap.com>
- Re: identical input, different output?
  - From: danielw@emaildoge.com

Prev by Date: Re: identical input, different output?
Next by Date: Re: identical input, different output?
Previous by thread: Re: identical input, different output?
Next by thread: Re: identical input, different output?
Index(es):
- Date
- Thread