Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 9 Jun 2015 12:13:09 +0300
From: Shinnok <admin@...nnok.com>
To: "john-dev@...ts.openwall.com" <john-dev@...ts.openwall.com>
Subject: Re: [Johnny] Task 1.6.1 Multiple cracking session management



> On 08 Jun 2015, at 23:11, Mathieu Laprise <mathlaprise@...il.com> wrote:
> 
> Shinnok,
>> On Mon, Jun 8, 2015 at 3:59 PM, Shinnok <admin@...nnok.com> wrote:
>> I'm also not 100% convinced anymore we need more than just session history at this point. This needs much more thinking and a couple more prerequisite tasks before we can embark in this journey, which could get hairy. Like the Settings one, Mathieu, so at this point that one takes priority over this one. After you finish the session history of course.
> Okay, I will do that. Which task are you referring to by the "Settings one" ? Are you talking about this issue https://github.com/shinnok/johnny/issues/9 or "when we load a session, we populate the UI with the settings(exemple check the --fork chekbox) ?
> 

Both should be handled in the same run. What we need is a wrapper class named JohnSession that encompasses all settings that define a cracking session. All values are still stored and loaded via QSettings. You can handle this one instead of multiple concurrent sessions.

I'll update the roadmap to reflect this change.

Shinnok 
[ CONTENT OF TYPE text/html SKIPPED ]

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ