|
Message-Id: <6201EA43-5C13-44C8-88C5-335475935AF3@shinnok.com> Date: Thu, 4 Jun 2015 22:04:12 +0300 From: Shinnok <admin@...nnok.com> To: john-dev@...ts.openwall.com Subject: Re: [Johnny] Task 1.5.1 Manual plaintext guessing > On Jun 4, 2015, at 10:03 PM, Shinnok <admin@...nnok.com> wrote: > >> >> On Jun 2, 2015, at 4:59 AM, Solar Designer <solar@...nwall.com> wrote: >> >> On Mon, Jun 01, 2015 at 05:03:34PM -0400, Mathieu Laprise wrote: >>> How is --stdin supposed to work ? I'm not sure to understand. I know for >>> sure that the password for one of my hash is "baseball". I did ./john >>> --stdin pw1.txt . I got a command line, I enter "baseball" and press ENTER. >>> A new command line appears to enter another word. How do I trigger the >>> attack with --stdin? >> >> Your guesses entered so far will actually be checked against the hashes >> when either all of the buffers fill up (stdin stream buffer and JtR's >> own plaintext keys buffer, the latter one of which is hash type and >> build specific) or there's EOF on the input stream. So in your specific >> example, you'd press Ctrl-D. In Johnny, you'd flush the Johnny-side >> buffer (if any exists) and then close the file descriptor. Obviously, >> this will also cause john to terminate once it's checked the plaintexts >> entered up to that point. > > Mathieu, is this working for you? I noticed in your latest revision you're closing the readChannel after writing the passphrase, which I'd assume is correct. *writeChannel
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.