[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20120421T213142-80@post.gmane.org>
Date: Sat, 21 Apr 2012 20:07:34 +0000 (UTC)
From: donovan <contact.newangels@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Extract the cracked pass from John.pot
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=";"
>
> While my previous remark seems to be on topic here, I'm afraid the
> following is off-topic on john-users, because it is related to usage of
> basic unix commands. So, this kind of question is better asked in a
> forum for unix users.
>
> Anyway, you might try
>
> export LC_ALL=C; grep -v ":*;" john.pot | cut -d";" -f 2- -s > test2.txt
>
> to get all those passwords from lines with a semicolon as a separator.
> the export makes sure that you avoid issues with illegal byte sequences
> due to passwords using an iso-8859-* encoding.
> The grep skips those lines with a colon as a separator, but a semicolon
> as part of the password.
> As a result, you would also miss the lines with a ";" as separator and a
> password containing a ":" and a ";" somewhere after the ":".
>
> Frank
>
>
Hello Frank,
Thanks again for your time, really appreciated.
I understand your explain about, i just past your command & = Blank file
I try with & without "LC_ALL=C" & the same = "test2.txt" = Blank
Also, you have to know the reason of my request, here ;
After some stats & tests, i realise, but you know that for sure...
many pass are the same than different algo's...
Hope you understand the sens of my words , sorry, my English speaking is poor.
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"
Example :
HERE the DES for the pass "frank"
lUwjiXB2Wq/t6
If i run an attempt on an MD5 list contain an Hashe corresponding to the pass :
frank, John don't find it , cause associated to DES.
Yesterday, with the plain extracted with the command you share, i run some list
based on different hashes & find with this WL many pass who are associated to
other hashes.
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.
Hope you can understand my bad speaking.
Regards,
Donovan
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.
