Date: Sun, 31 May 2015 17:05:22 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: [john-core] Getting John's stdout unbuffered for Johnny On 2015-05-31 15:01, Solar Designer wrote: > However, I am not sure this was such a good idea. Even with these > exceptions, there may still be cases where the buffering was helpful. > For example, I sometimes run "./john ... > /dev/null" when I am testing > on huge numbers of easily crackable hashes. Line buffering will make > this run considerably slower. Maybe this means that we need a --quiet > or --silent option or/and a key or/and a john.conf setting to mute > printing of guesses to stdout. FWIW, Jumbo has it as --verbosity=N where default is 3. This is used for a variety of things. At -verb=1, printing of cracked hashes (as well as stdout candidates) is muted. magnum
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.