Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 9 Jun 2015 15:59:44 +0300
From: Shinnok <>
To: "" <>
Subject: Re: [Johnny] Task 1.6.1 Multiple cracking session management

> On 09 Jun 2015, at 14:40, Mathieu Laprise <> wrote:
>> On Tue, Jun 9, 2015 at 5:13 AM, Shinnok <> wrote:
>> 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.
> Now that we save/can load multiple sessions with history rather than the "one and only default.johnny", is using QSetting still the best approach or should we save the informations about the session's UI settings(ex: --fork is checked) directly in the appropriate .johnny file which contains the files and format at the moment.

We can force direct qsettings to an any .INI file format. Aren't we already doing that for the .johnny file? If yes then it's just a matter of switching to a single practice.

Content of type "text/html" skipped

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.