[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e6f7dcc989f24ae43cd85393c9a1f1c4@smtp.hushmail.com>
Date: Thu, 13 Aug 2015 11:29:14 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Question regarding --crack-status
On 2015-08-13 10:53, Shinnok wrote:
> We're currently using a john --show handler to update cracked passwords at every n seconds (configurable) for both core and jumbo during a running attack. I'm currently pondering the possibility of replacing the handler and timer with --crack-status for Jumbo case, given that we have a solution for the stdout issues.
>
> The question being, is --crack-status reliable enough to be used for this purpose? Is there any chance that it skips certain cracks for various reasons?
--crack-status simply emulates a keypress every time a password is
cracked, and should be just as reliable or not (any delays you
experience pressing a key will also happen here).
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.
