[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+E3k91uSA_eiTyNyHk=mjZsrJwLh2wmA2WQ=E=kPbqEDmwyPg@mail.gmail.com>
Date: Fri, 14 Aug 2020 12:16:10 -0800
From: Royce Williams <royce@...ho.org>
To: john-users@...ts.openwall.com
Subject: automating --fork with ZTEX and variable device counts
Any tips for automating the use of --fork when the number of ZTEX boards
can vary with device stability? (I've read OPTIONS and FAQ and don't see
anything I can leverage.)
Since a board or two sometimes drifts in and out, hard-coding the fork
count (so that it matches the number of devices specified on the
commandline, etc) works for a while, but then if a board reappears or
drops, the device count isn't cleanly divisible by the number of forks
anymore, so john exits. This is manageable when doing individual
interactive runs of john, but does not lend itself well to loops or
automation.
Since the fork count is validated at runtime after starting john, even if I
had a way to reliably check device count externally, the device count can
(and does) change between when the check is performed and when john is
started. So it seems that a pre-runtime check would not be useful to handle
this case.
--
Royce
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.
