Date: Fri, 05 Jun 2015 09:21:41 +0200 From: Frank Dittrich <frank.dittrich@...lbox.org> To: john-dev@...ts.openwall.com Subject: Re: [Johnny] Task 1.6.1 Multiple cracking session management On 06/05/2015 09:06 AM, Shinnok wrote: > Yes. That is multiple concurrent cracking sessions via a tabbed > interface. What you implemented so far is just session history, keep > working on it though as it'll get its own task. I like the screenshot > you have on Github, but wee need to do something about the names. The > dates are not enough, maybe also add the source password files as > tooltips. Later maybe we should be able to name sessions. Isn't allowing end users to run multiple john sessions in parallel asking for trouble? I think providing help to not accidentally overwrite old .rec files, suggesting which of the existing sessions were most successful (number of cracks for a given hash type per time) and which should be resumed first for the best result etc. might be much more helpful. If you allow multiple sessions at once, you cannot provide these numbers any longer, because you never know the system load during these sessions. (OK, you don't *know* that even if you don't allow multiple john sessions at the same time, but I think it is OK to assume almost no other load in this case.) Frank
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.