phc-discussions - Re: [PHC] Supporting AVX2/SSE2 or not with a single binary

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1708627211.396577.1395351246550.open-xchange@email.1and1.com>
Date: Thu, 20 Mar 2014 16:34:06 -0500 (CDT)
From: Steve Thomas <steve@...tu.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Supporting AVX2/SSE2 or not with a single binary

>  On March 19, 2014 at 9:39 PM Steve Thomas <steve@...tu.com> wrote:
> 
>  Bill don't try to learn SS*E*/AVX* from the blake2-ref code... besides being
>  buggy.
> 

So I finally got around to almost reporting the endian assumption bug
in one of the *_init_param functions when I found out I was looking at
the SSE  version. I started looking at the SSE then switch to the ref code.
I had blake2b.c, blake2b-ref.c, both blake2.h and few  other .h files open.
I was being stupid.

Sorry Samuel Neves I was wrong.
Content of type "text/html" skipped