[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6iqNonFs5_=xRWNOuth3H_-KLku7rJ2ox8HA8m-DtFNdhQ@mail.gmail.com>
Date: Mon, 10 Sep 2012 20:28:33 +0200
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Cracking Mountain Lion hashes (WIP)
2012/9/10 Dhiru Kholia <dhiru.kholia@...il.com>:
> It is not my code ;). Lukas wrote it. I can see if this can be fixed easily.
>
> Lukas,
>
> Any comments? I think we already calculate variables salt's length
> correctly. We just need to apply the same code to actual hash string.
> Correct?
Sorry for not being active in this thread. I have exams on my head for
the next 2 weeks, after that I'll be back on john-dev activity.
First of all I want to thank Dhiru for addding proper OpenMP code.
My opinion is following:
1) we should have format named "pbkdf2-sha512" in cpu, opencl and cuda versions
2) this format should accept possible common ciphertexts formats
(simple modifications to valid() and salt() for every ciphertext
format) - for now it should accept grub in it's native form ans
"pbkdf2-sha512$...."
3) we do not want fixed salt length's
If someone have time and will to work on this please do and do not
forget add yourself to the copyright note.
If you have any other ideas just do it. I do not consider this code as
mine, rather as ours. Any reasonable changes in code is welcomed.
If no one else have time to play with this code, or have more
fascinating things to do I'll take care of this format after my exams.
Take care,
Lukas
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.
