praktiskt / multi-john Goto Github PK

Currently, the "worker" is interchangeably used with "node", which is what JtR refers to in through it's flags when running multiple instances of JtR (--node=x/y).

It makes sense to refactor into something else, more concisely. It is very easy to get them mixed up. A node is something that we run for John, whereas a worker is something that multi-john runs (which wraps around a node).

Prerequisite: #2

If a session is identical to a restarted one, we should be able to just resume it.

There should be a custom image of John which could allow the project to...

• build for different architectures
• build with GPU support
• build with different versions of John

When a worker is killed, there is no way to recover it. We should be able to recover a worker if it is restarted with the exact same configuration.

State could likely just be pushed to etcd under some prefix when a worker is killed, and similarly a worker should check for existing state when it's started.