Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 5 Jun 2015 10:06:37 +0300
From: Shinnok <>
Subject: Re: [Johnny] Task 1.6.1 Multiple cracking session management

> On Jun 5, 2015, at 12:25 AM, Mathieu Laprise <> wrote:
> On Thu, Jun 4, 2015 at 5:02 PM, Mathieu Laprise < <>> wrote:
> On Thu, Jun 4, 2015 at 2:56 PM, Shinnok < <>> wrote:
> My original task was for supporting multiple cracking sessions via a tabbed interface.
> Aleksey said:
> Oh, does not it include running of multiple john instances at the same time?
> Shinnok said:
> No. There is one question regarding the implementation though. I was hoping we could just use --session to do this, but then we'd either have to teach Johnny to parse a .rec so that we can extract the options and translate them to the UI on session restore or store them using QSettings also. 
> And in the thread about stdout/stdin Shinnok said :
> After some more thought, we do have to figure out and start working on a solution for both stdout and stdin. For the latter, if we take into consideration the concurrent cracking sessions feature, both of these:
> 1. kill process group on *nix for FORK case
> 2. ConsoleCtrlEvent CTRL_C_EVENT on Windows 
> Will fail dramatically by killing all spawned JtR attack sessions. So for the future, the ability to send q to a JtR session is critical, amongst other needs
> I'm really confused, the first two messages from the proposal discussion lead me to believe we always have only one instance of john running even though we have multiple tabs, and the new message from the stdin/stdout thread leads me to believe the opposite.
> Shinnok,
> Is your plan to start ./john --session=1 --format=aix-smd5 /home/math/pw1.txt ; ./john --session=2 --format=aix-smd5 /home/math/pw1.txt etc... running at the same time ? It's the same john executable but we have multiple "john process" running.

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.

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.