08-25-2017, 06:04 PM
(This post was last modified: 08-25-2017, 06:04 PM by Chick3nman.)
As far as timing how long it takes, it does not look like there's any inbuilt function to handle this sort of thing(feature request maybe?). That said, the total bruteforce time and the time remaining will not be inconsistent so after restarting and eventually finding your plaintext(assuming you do find it before exhausting the keyspace) you can easily subtract the last given time remaining from the initial time remaining when you first started to see how long it took.
For example:
Lets say your attack will exhaust in 3 days total. You start and stop it a few times and then you find the password you are after. Right as you find the password, the status says you still have 1 day remaining to exhaust the keyspace. You can easily subtract 1 from 3 and find out that it took 2 total days of cracking, regardless of when those 2 days actually happened.
For example:
Lets say your attack will exhaust in 3 days total. You start and stop it a few times and then you find the password you are after. Right as you find the password, the status says you still have 1 day remaining to exhaust the keyspace. You can easily subtract 1 from 3 and find out that it took 2 total days of cracking, regardless of when those 2 days actually happened.