Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b8b3cd4912d37b8c7d52c35b056a58da@smtp.hushmail.com>
Date: Mon, 27 May 2013 07:35:25 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: disabling retrieval of cracked passwords

On 27 May, 2013, at 7:03 , Royce Williams <royce@...ho.org> wrote:
> On Fri, May 24, 2013 at 1:37 PM, magnum <john.magnum@...hmail.com> wrote:
>> On 23 May, 2013, at 6:18 , Royce Williams <royce@...ho.org> wrote:
>>> Can JtR be run in such a way that the results show that a password was
>>> cracked, but the cracked passwords themselves are not recorded?
>> 
>> With latest "bleeding" revision, you can say --verbosity=1 for not showing the cracks.
> 
> Hey, much obliged!  I hadn't even gotten a chance to try the .pot ->
> /dev/null idea that RB had, and there's already code!  That's pretty
> cool of you, sir.  I'll check it out.

You still need to link .pot to /dev/null (or use Jumbo option "-pot=/dev/null" in case that works, I haven't tried). The -verb=1 just mutes the writing of cracks to the console.

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.