[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <E562634A-30C2-4FF4-BF59-639BF09C2054@shinnok.com>
Date: Thu, 4 Jun 2015 21:59:27 +0300
From: Shinnok <admin@...nnok.com>
To: john-dev@...ts.openwall.com
Subject: Re: [Johnny] Task 1.6.2 Ability to select/deselect individual hashes in a cracking session
> On Jun 2, 2015, at 9:38 PM, Mathieu Laprise <mathlaprise@...il.com> wrote:
>
> Task 1.6.2 is the ability to select/deselect individual hashes from being handled in a cracking session(maybe via a simple checkbox to each row?).
>
> To implement this, I think about when user click "Start Attack", we'll create a new file pwCopy.txt with only the selected rows. Do you have another idea ?
>
> The problem I can think of is related to "open last session".
> 1) If we use a new file pwCopy.txt, we will probably have to open this one in the password tableView instead of the original file with all the rows to be coherent with the file in the .rec.
> OR
> 2) Open the original file with all rows, but the .rec won't be coherent. Should we modify it ?
> 2.1 Wouldn't it be weird that the "open last session" don't save the checkboxes state in the password tableview ? I mean the "real last session" didn't process all rows of the files and this attack will process all of them if the user don't uncheck some of them again.
> 2.2 However, if the file was edited outside Johnny and we saved the checkboxes states, we might get weird behavior.
If you read my latest reply in the sessions thread,
It would be taken care of by properly storing Johnny's attack options for a session via QSettings, excluded hashes/rows would be a setting too.
Shinnok
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.
