Currently, the endpoint to start the attack waits for keyspace claculation to complete. This can take several minutes and be a bit confusing, despite the new UI information.
The endpoint should return in under < 500ms, and only capture a keyspace calculation error if it returns quickly.
This might make error logging a bit difficult however, so might need to add errors into the attack status itself.
Currently, the endpoint to start the attack waits for keyspace claculation to complete. This can take several minutes and be a bit confusing, despite the new UI information.
The endpoint should return in under < 500ms, and only capture a keyspace calculation error if it returns quickly.
This might make error logging a bit difficult however, so might need to add errors into the attack status itself.