[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90dc2a36b3b3783e7bf686ac17455daa@smtp.hushmail.com>
Date: Sat, 21 Apr 2012 23:43:16 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Re: Extract the cracked pass from John.pot
On 04/21/2012 10:07 PM, donovan wrote:
> Frank Dittrich <frank_dittrich@...> writes:
>> For some reason you do have lines in your pot file where a semicolon
>> instead of a colon separated the hash and the password.
>> May be you invoked john with --sep=";"
...
>> you might try
>>
>> export LC_ALL=C; grep -v ":*;" john.pot | cut -d";" -f 2- -s > test2.txt
>>
...
> I understand your explain about, i just past your command & = Blank file
>
> I try with & without "LC_ALL=C" & the same = "test2.txt" = Blank
I believe Frank made a typo. It should be grep -v ":.*;" (with a dot
added before the asterisk), like this:
export LC_ALL=C; grep -v ":.*;" john.pot | cut -d";" -f 2- -s > test2.txt
Though I haven't tested this.
> In fact, many hashes, MD5, SHA1 or whatever hashes contain same pass exist
> allready in john.pot, but if you run an attempt on an MD5 list & if john
> identify the corresponding hashe no prob', is the goal of "John", but if the
> plain pass exist in john.pot but associated to an DES Line, John dosen't give
> you the plain of the MD5 pass, logical, cause associated to the MD5 , But exist
> allready in the "pot"
...
> The WISH ! will be if it's possible for sure for DEV team & for the the Next
> versions of John to make some code for cross pass identification.
Next Jumbo will (if Solar accepts that patch) have some support for
using pot files as wordlists. For example:
john -wo hashes.txt
will use john.pot as a wordlist, and parse it correctly (but dupes are
not removed yet, so it might be slower than needed). And,
john -wo:tab.pot -field-sep=tab
will get words from "tab.pot" file, parsed using tab delimiter.
The simple "heuristics" are:
1. if --wordlist given without a name, use default pot file
2. if wordlist name (after 1) ends in .pot, parse it as such (taking
--field-sep-char into account)
If you want to try that code, latest bleeding-edge code is available as
a zip file at
https://github.com/magnumripper/magnum-jumbo/zipball/magnum-jumbo
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.
