[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150601100232.GC29213@openwall.com>
Date: Mon, 1 Jun 2015 13:02:32 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: [john-core] Getting John's stdout unbuffered for Johnny
On Mon, Jun 01, 2015 at 09:30:42AM +0300, Shinnok wrote:
> On May 27, 2015, at 10:56 PM, magnum <john.magnum@...hmail.com> wrote:
> > As far as I'm aware it treats input as a TTY if it is indeed a TTY, nothing weird about that. It doesn't default to reading candidates, there's an option for that.
>
> If that's not the case, then maybe we need _IONBF for stdin on JtR for the non-tty and non stdin cases too. I can't get a char from Johnny to JtR.
What char are you trying to send and why? I guess you're doing this to
trigger the status line, or you're sending 'q' to have it quit gracefully,
right? If so, the first hurdle is that currently JtR would expect that
char to come from its tty, not from stdin.
> Mathieu, after you confirm the stdout change from Solar it would be good to test the stdin part to JtR. Go into the update method and write a character to JtR. and look for the update line from JtR. Then try with '\n'; after that try with fflush() on Johnny's side. Then we can proceed to trying the _IONBF on JtR side.
I don't expect any of this to work for the reason above. I don't mind
Mathieu confirming this, though. And then we'll need to add --no-tty or
something like that.
Alexander
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.
