[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a5988e55f68d5fe26cc344c0d8dad5ac@smtp.hushmail.com>
Date: Sun, 26 May 2013 19:55:10 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Couple of recent changes in bleeding
Not sure when it happened but I get this on Bull now:
$ make -s clean && make -sj8 linux-x86-64-xop
sse-intrinsics.c: In function 'SSESHA256body':
sse-intrinsics.c:1348:3: warning: implicit declaration of function 'SWAP_ENDIAN' [-Wimplicit-function-declaration]
sse-intrinsics.c: In function 'SSESHA512body':
sse-intrinsics.c:1674:4: warning: implicit declaration of function 'SWAP_ENDIAN64' [-Wimplicit-function-declaration]
sse-intrinsics.o: In function `SSESHA256body':
sse-intrinsics.c:(.text+0xa07a): undefined reference to `SWAP_ENDIAN'
sse-intrinsics.c:(.text+0xa0a7): undefined reference to `SWAP_ENDIAN'
sse-intrinsics.c:(.text+0xa0e0): undefined reference to `SWAP_ENDIAN'
sse-intrinsics.c:(.text+0xa119): undefined reference to `SWAP_ENDIAN'
sse-intrinsics.c:(.text+0xa152): undefined reference to `SWAP_ENDIAN'
sse-intrinsics.o:sse-intrinsics.c:(.text+0xa18b): more undefined references to `SWAP_ENDIAN' follow
sse-intrinsics.o: In function `SSESHA512body':
sse-intrinsics.c:(.text+0xdbf7): undefined reference to `SWAP_ENDIAN64'
sse-intrinsics.c:(.text+0xdc0a): undefined reference to `SWAP_ENDIAN64'
sse-intrinsics.c:(.text+0xdc64): undefined reference to `SWAP_ENDIAN64'
sse-intrinsics.c:(.text+0xdc77): undefined reference to `SWAP_ENDIAN64'
sse-intrinsics.c:(.text+0xdcd1): undefined reference to `SWAP_ENDIAN64'
sse-intrinsics.o:sse-intrinsics.c:(.text+0xdce4): more undefined references to `SWAP_ENDIAN64' follow
collect2: ld returned 1 exit status
make[1]: *** [../run/john] Error 1
make: *** [linux-x86-64-xop] Error 2
magnum
On 25 May, 2013, at 16:06 , <jfoug@....net> wrote:
> I added the aix-* hashes to pass_gen.pl. I had to figure out how to do the base-64 properly, and how to use SHA512 in Crypt::PBKDF2. Once those were done, it generates hashes perfectly.
>
> Added 125 byte long password hashes to all aix-* formats. Since using pbkdf2_hmac_sha*.h files, the PLAINTEXT_LENGTH was kicked up to 125 bytes, but we had no test data. It would be VERY wise to go through all the formats, and add test data that pushes the max PLAINTEXT_LENGTH, so that we know the formats are working.
>
> I changed the pbkdf2_hmac_sha*.h files, so that they can optionally also include the CTX (oSSL) code, even if building under SSE2. This allows the 1 password / 1 hash interface of oSSL to be used also. This was needed in the next change (in cmp_exact)
>
> I changed the pbkdf2-hmac-sha512-fmt-plug.c to use pbkdf2_hmac_sha512.h. The pbkdf2 code originally in the format was 2x slower (doing 4 SHA512 crypts per loop, vs 2). Also gained, is SSE2. The oSSL is about 2x faster than before. If built with SSE, it is 4x faster (or more). XOP should gain more.
>
> I am going to look at adding SSE to cryptsha256. That will be a bit of a challenge, since it is a mix of 1 and 2 limb crypts, AND the mix varies based upon password length. Thus, I will probably have to rearrange the order of passwords within the crypt, but being very careful to properly update the original order of the passwords into the crypt array. The new SHA256 does have a 'flat' input mode, and that may be helpful for getting this to work easier. I will have to see in the end if flat helps, or if intermixed ends up 'winning' in the end. It may be that both ways have to be used. In SHA4 builds, it may be faster to keep the inputs in flat mode.
>
> Jim.
>
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.
