[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2fe779d5.17b0e0d5.51dd5219.a0bee@o2.pl>
Date: Wed, 10 Jul 2013 14:22:49 +0200
From: marcus.desto <marcus.desto@...pl>
To: john-dev@...ts.openwall.com
Subject: Re: PBKDF2 hash_out treatment
Additional note accourding to pbkdf2_hmac_sha1_unsplit_kernel.cl :
password = "password"
passwordSalt = "123456789012345678901234"
and 1 Iteration
should result
4187d67b5f27ec26f8dd3493699c81952444
But it does not.
Marcus
Dnia 10 lipca 2013 14:19 marcus.desto <marcus.desto@...pl> napisał(a):
> magnum,
>
> I think I have found the problem.
>
> It is the salt size. My reference input contained a salt with size 32. As I switched to 4 (your test input), the opencl implementation worked well with pyopencl.
>
> Now. I tried different lengths of salt. Finally, I can confirm, that pbkdf2_hmac_sha1_unsplit_kernel.cl produces wrong hashes since length of the input salt string is >23.
>
> I would like to mention that I did not convert the input strings to UTF-8.
>
> In pbkdf2_hmac_sha1_unsplit_kernel.cl I set
>
> #define KEYLEN 20
> #define OUTLEN 87
> #define SALTLEN 32
>
> Remaining pbkdf2_hmac_sha1_unsplit_kernel.cl has not been modified, except
>
> inline void pbkdf2(__global const uchar * pass, uint passlen,
> __global const uchar * salt, uint saltlen, uint iterations,
> __global uint * out, uint outlen)
>
> into:
>
> __kernel void pbkdf2(__global const uchar * pass, uint passlen,
> __global const uchar * salt, uint saltlen, uint iterations,
> __global uint * out, uint outlen)
>
> because I am accessing the data not using struct.
>
> Regards,
> Marcus
>
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.
