Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 5 May 2015 15:22:55 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: [Johnny] Task 1.4.2 fork and OpenMP

Shinnok, Mathieu -

On Tue, May 05, 2015 at 06:33:03AM +0300, Shinnok wrote:
> > On Apr 30, 2015, at 3:04 AM, Mathieu Laprise <mathlaprise@...il.com> wrote:
> > //     // When we want to get John status we send enter to John. Then
> > //     // John write something to its stdout. We do not need to read its
> > //     // output here because when output is ready to be read a signal is
> > //     // fired and we read John output with status as any other John's
> > //     // output.
> > //     // TODO: However it does not work as of we do not have terminal.
> > //     // TODO: Why do we write to John even when it is not running?
> > //     m_johnProcess.write("a\r\n");
> > // }
> 
> Unfortunately this is a JtR perk. I'm looking in tty.c:
> void tty_init(int stdin_mode)
> 
> and it expects one of these two possible states:
> 1. Stdin mode; this is the mode that Johnny's usage via QProcess falls into and why writing "a\r\n" doesn't work, it's probably taken as a wordlist input
> 2. Explicit tty mode;
> 
> We need to find middle ground for Johnny's sake.

If we need John to print status, the official way to do so is by sending
it SIGHUP.  This makes it print status and update the .rec/.pot/.log files.

Alexander

Powered by blists - more mailing lists

Your e-mail address:

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