02-27-2016, 08:34 AM
Hi,
It looks like the outfile-check-dir is just being ignored? I've got 2 machines with a shared nfs directory '/results'
This is what I run on both machines:
Node 1:
./cudaHashcat64.bin --outfile-format=2 -m 2500 -a 3 /hccap/testme.hccap ?d?d?d?d?d?d?d?d?d?d -o /results/node1 --outfile-check-dir=/results --outfile-check-timer=10
Node 2:
./cudaHashcat64.bin --outfile-format=2 -m 2500 -a 3 /hccap/testme.hccap ?d?d?d?d?d?d?d?d?d?d -o /results/node2 --outfile-check-dir=/results --outfile-check-timer=10
When node 1 cracks the hash, node 2 just keeps running until the entire keyspace is exhausted. What I would expect is for it to terminate in 10 seconds after the first node cracks the hash. Is there any specific naming convention required for outfiles?
It looks like the outfile-check-dir is just being ignored? I've got 2 machines with a shared nfs directory '/results'
This is what I run on both machines:
Node 1:
./cudaHashcat64.bin --outfile-format=2 -m 2500 -a 3 /hccap/testme.hccap ?d?d?d?d?d?d?d?d?d?d -o /results/node1 --outfile-check-dir=/results --outfile-check-timer=10
Node 2:
./cudaHashcat64.bin --outfile-format=2 -m 2500 -a 3 /hccap/testme.hccap ?d?d?d?d?d?d?d?d?d?d -o /results/node2 --outfile-check-dir=/results --outfile-check-timer=10
When node 1 cracks the hash, node 2 just keeps running until the entire keyspace is exhausted. What I would expect is for it to terminate in 10 seconds after the first node cracks the hash. Is there any specific naming convention required for outfiles?