Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20120420T053423-18@post.gmane.org>
Date: Fri, 20 Apr 2012 03:38:28 +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:

> 
> On 04/19/2012 06:52 PM, donovan wrote:
> "don't work" really isn't a good description of your problem.
> Better would have been to mention what result you expected and what
> result you got. Otherwise, people can only guess.
> 
> As already mentioned, you should use -f 2- just in case there are
> passwords containing colons.
> 
> If your problem is that john,pot contains lines with another separator
> instead of a colon, you have to adjust the -d option accordingly.
> 
> If your problem is that you have mixed lines in john.pot, some with a
> colon as a separator, some without a colon, you might want to add the -s
> option, to skip all lines which don't contain a colon.
> 
> If your problem is that you wanted to see the cracked passwords on the
> screen (instead of redirecting output into a file), you could have used
> 
> cut -d; -f 2- -s john.pot | less
> 
> Assuming less exists on Mac OSX, otherwise try more instead, or just use
> cut -d; -f 2- -s john.pot
> 
> Frank
> 
> 


Me again, sorry, just realize i make an mistake in my reply about the POT
file format...

For sure the POT file appear in "HASHE:PASS" & NOT in :hashe:pass

So for resume, just need to skip the hashes & output the pass only into an file.

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.