Date: Thu, 14 May 2015 19:19:05 +0300 From: Shinnok <admin@...nnok.com> To: john-dev@...ts.openwall.com Subject: Re: problem with signal handling in core john (was: [core john] [Johnny] Windows event loop) > On May 14, 2015, at 4:10 PM, Aleksey Cherepanov <lyosha@...nwall.com> wrote: > > On Thu, May 14, 2015 at 03:23:34PM +0300, Shinnok wrote: >> >>>> The patch maintains event processing(including CTRL_C) under the console(CMD) while also allowing for Johnny to properly terminate JtR instances via the same CTRL_C_EVENT. >>> >>> As I understand from previous mails, john work under cmd.exe well, but >>> when it is called from a program that disabled handling of ctrl-c for >>> itself (like Johnny, but not limited to it) john inherits that >>> disabled handling and does not enable it. Shinnok - am I right? >>> >> >> That is correct. > > So theoretically johnny can solve it on its own: enable ctrl-c > handling before each calling of john and disable after it, can't it? > I didn't try this approach. If you or Mathieu decide to do it, make sure you test all possible variants, like I did. Shinnok 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.