[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150511133056.GA13502@openwall.com>
Date: Mon, 11 May 2015 16:30:56 +0300
From: Aleksey Cherepanov <lyosha@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: [core john] [Johnny] Windows event loop
Shinnok,
On Mon, May 11, 2015 at 04:06:32PM +0300, Aleksey Cherepanov wrote:
> On Mon, May 11, 2015 at 03:34:00PM +0300, Shinnok wrote:
> > Is #2 the helper executable one? If so, then I'm afraid that is not the most viable solution for the long term.
> >
> > The way to go is this:
> > 1. For now implement the event loop and handle WM_CLOSE. JtR core would be best.
>
> Assuming #2 is properly implemented (and Mathieu won't waste a lot of
> time debugging it for release), I think that WM_CLOSE may be not very
> important now.
Explain the reasons to not use the helper program and implement
WM_CLOSE please.
> > 2. Further along the road we should convert to --no-tty option and then we can close JtR just by sending a "q\n".
> >
> > I'm happy with just supporting a specific version of JtR going forwards and not looking backwards. Johnny is supposed to run on modern desktops and there's no reason why such a desktop can't run a fresh JtR.
Can't we use the helper program till --no-tty interface introduction
skipping WM_CLOSE step?
Thanks!
--
Regards,
Aleksey Cherepanov
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.
