[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee5e12723056339db6c7419120dc2549@smtp.hushmail.com>
Date: Mon, 5 Nov 2012 20:45:16 +0100
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Need help with hashes from isocode plaintext
On 5 Nov, 2012, at 2:41 , wfdawson <wfdawson@...lsouth.net> wrote:
> On 4 November 2012 07:55, wfdawson <wfdawson@...lsouth.net> wrote:
>> I'm having some difficulty grasping how to make JtR work for hashes from unicode plaintext. I'm sure I'm missing something very basic.
>
> md5 does not do unicode. So the special a in there is going to be the
> ansi interpretation of unicode.. the ansi characters 0xC3 and 0xA4
Some systems actually do an MD5 of UTF-16 encoded plaintext, which I guess is what Stephen meant by "unicode". Our 'raw-md5u' format supports that format. Also, 0xC3, 0xA4 is UTF-8, not ANSI. The "ANSI codepage" normally refers to iso-8859-1. Then it's a single 0xE4.
> Thanks for your comments. I'm sorry if I'm a bit obtuse on this question - ordinarily, I would not have such difficulties. Unfortunately, I'm still not able to crack it.
>
> Can you or anyone show a wordlist and corresponding execution of john to crack the hash
> 005f3942106f3bc5a392dcde686d87f0 and give the plaintext geländerxx? I believe I should properly understand it from a working example.
$ echo -n geländerxx | iconv -t utf-8 | md5sum
2bfba679d5817bd26fef35e70a07f00a
OK, so it's not UTF-8. My second guess would be cp1252 or iso-8859-1 (they are the same for this letter):
$ echo -n geländerxx | iconv -t iso-8859-1 | md5sum
005f3942106f3bc5a392dcde686d87f0
There you have it. Note the '-n' option to echo. Without it you will get a totally different MD5 because you will include a linefeed in the hashed string.
magnum
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.
