Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4cd73ff1-9b01-3129-45dc-c0d80dd7236a@matlink.fr>
Date: Fri, 4 Nov 2016 16:13:22 +0100
From: matlink <matlink@...link.fr>
To: john-users@...ts.openwall.com
Subject: Re: John does not fork as many times as I want



Le 04/11/2016 à 16:06, Solar Designer a écrit :
> On Fri, Nov 04, 2016 at 04:00:30PM +0100, matlink wrote:
>> Le 04/11/2016 ? 15:56, Solar Designer a ?crit :
>>> Sure, "--restore" continues from where the session was interrupted, not
>>> re-testing the previously tested candidate passwords.
>>>
>>> Without that option, you have JtR re-test the same candidate passwords.
>>>
>>> The pot file eliminates previously cracked hashes in either case.
>> Well, I was not using the --restore option, but always the --session
>> with --pot and in fact, when john starts it says "Remaining 25185227
>> password hashes with no different salts" which is less than when
>> previously ran. I guess --restore is equal to running john with the same
>> parameters as before. That was my question.
> Your guess is wrong.  "--restore" is more than that, and it is usually
> much more efficient than starting over with the same parameters.
>
> However, since you were getting forked processes not started or killed,
> you did in fact have to start over not to miss any weak passwords.

Alright. Is starting over meaning re-testing the whole potfile against
the hashed pwd? The said potfile is about 670MB, then is not using
--restore having a huge impact about performances? What if that file
were much more huge, like 50GB?


>
> "Remaining 25185227 password hashes" is low enough that you should be
> able to run 40 processes now, if you skip the "single crack" mode as I
> suggested.
>
> Alexander

-- 
Matlink - Sysadmin matlink.fr
Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/
XMPP/Jabber : matlink@...link.fr
Clé publique PGP : 0x186BB3CA
Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2

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.