Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 29 Jun 2011 22:39:12 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: IPB2 and syntax - same question but still confuse

On Sun, Jun 26, 2011 at 10:31:03AM +0200, websiteaccess@...il.com wrote:
>  I have compiled john 1.7.7 jumbo6 (os X, 64 bits).
> 
> I have the following hash  user:6e8bb151fbed7cee93acf6b0288c79a7	
> r{)<|    =  IPB2 format
> 
>  I convert it to 
> 
> user:$IPB2$727b293c7c$6e8bb151fbed7cee93acf6b0288c79a7
> 
> It works with "mpirun -np 4 ./john64 -format=IPB2 -i:alnum hash.txt"
> 
> but it's very boring to convert more than 10 hashes to that format.

You could do it with a script.

> I tried 
> 
> user	 (tab) md5_gen(12)6e8bb151fbed7cee93acf6b0288c79a7$r{)<|
> 
> iMac-de-xxx-xx:run xxxxx$ mpirun -np 4 ./john64  -i:alnum dream.txt 
> -field-separator-char="(tab) "
> using field sep char '	' (0x09)
> No password hashes loaded (see FAQ)

If you have a space character after the TAB, as you have shown, then
that's the problem.  Remove it from both places (the file and the
option's parameter).  Without that extra space character, your hash
loads fine for me:

user	md5_gen(12)6e8bb151fbed7cee93acf6b0288c79a7$r{)<|

./john -field-separator-char='	' pw-ipb2

In both places, the whitespace is a single TAB character.  On bash
command-line, I typed it by pressing Ctrl-V and then TAB.

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.