Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 10 Jun 2013 08:02:19 +0200
From: magnum <>
Subject: Re: popular binary_hash_*

On 10 Jun, 2013, at 2:53 , Lukas Odzioba <> wrote:
> 2013/6/10 Lukas Odzioba <>:
>> Name fmt_default_binary_hash_N(void * binary) is ok?
> I assumed that and fixed opencl_*_fmt.c files.
> Also I changed labels for Keccak:
> -#define FORMAT_LABEL		"raw-keccak-256"
> +#define FORMAT_LABEL		"Raw-Keccak-256"
> -#define FORMAT_LABEL		"raw-keccak"
> +#define FORMAT_LABEL		"Raw-Keccak"

This is committed.

> This is what's left:
> ./opencl_nt_fmt.c:static int binary_hash_6(void *binary) { return
> ((unsigned int *)binary)[1] & 0x7FFFFFF; }

This is coalesced and out of order so shared functions can't be used.

> ./opencl_xsha512_fmt.c:static int binary_hash_6(void *binary) { return
> *((ARCH_WORD_32 *) binary + 6) & 0x7FFFFFF; }
> ./opencl_rawsha512_fmt.c:static int binary_hash_6(void *binary) return
> *((ARCH_WORD_32 *)binary+6) & 0x7FFFFFF; }

These have some sort of GPU-side comparison.

> Some of the formats had debug info inside binary_hash_0 function, I
> left them as is.

We might want to add debug code to the shared functions instead.


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.