[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <A51FD20A-639A-4A7B-8CDA-B951D43EE8E0@shinnok.com>
Date: Wed, 27 May 2015 21:09:48 +0300
From: Shinnok <admin@...nnok.com>
To: john-dev@...ts.openwall.com
Subject: Re: [john-core] Getting John's stdout unbuffered for Johnny
Mathieu,
Your description of the problem is too hasty. You need to do a more informative writeup based on the Github discussion, so that the JtR developers understand the problem from Johnny's perspective and provide useful feedback from JtR's perspective. With the current definition, I don't expect anyone to weigh in.
You need to describe the two Johnny problems:
1. Console log output;
2. Getting status lines from JtR(gratuitous or on-demand; for additional functionality and monitoring);
And the three solutions:
1. flush() and writing '\n'
2. prospective --no-tty option could be unbuffered (setbuf(stdout, NULL))
3. --progress-every && --crack-status
Shinnok
> On May 27, 2015, at 3:50 AM, Mathieu Laprise <mathlaprise@...il.com> wrote:
>
> I forgot to say in my last message that, on the other hand, if I don't add fflush(stdout), I'll only get the message after I terminate John.
>
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.
