[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20120422T002059-628@post.gmane.org>
Date: Sat, 21 Apr 2012 22:21:27 +0000 (UTC)
From: donovan <contact.newangels@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Extract the cracked pass from John.pot
magnum <john.magnum@...> writes:
> 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.
> 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
>
>
Hi Again Magnum,
Thanks for your reply & time.
Ok, first ;
1/ i type the purpose command, & got the test2.txt file with plain pass output,
but ! = 33 KO file !
My pot is 221 MO
2/ thanks for ready the reply about the reason of my request & i am verry happy
to read is on the "wish list" that will really great & an powerfull +
3/ I download your JTR version & going to make some try with ( have to compile
for MAC Before), i let you know about once all is done.
Concern, this version, may i have to tweak the paramater.h file for push the
lengh up or your allready dot & fixed ?
Thanks again
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.
