search

hashview / hashview-old

A web front-end for password cracking and analytics
http://www.hashview.io
GNU General Public License v3.0
619 stars 134 forks source link

Incorrect estimated time displayed when runtime is limited in bruteforce job #371

Closed GrepItAll closed 6 years ago

GrepItAll commented 6 years ago

image

The time estimated in this screenshot is 6 days 23 hours, but this is actually the time that the runtime is limited to. The actual estimated time is not displayed.

I believe this is because you are just splitting on ':' to parse the output of the hashcat thread, which immediately precedes the time limit.

i128 commented 6 years ago

I'm not able to replicate, what task are you running where you see this? (presuming raw). Is this from the local agent or a remote?

GrepItAll commented 6 years ago

Correct, raw brute. In my global settings, I had a runtime limit of 604,800s = 7days, hence the 6 days 23 hours remaining piece.

This is a local agent.

i128 commented 6 years ago

Bug is with split on ': ' as mentioned above. Currently pulls -1 in the index, switching to slice (19...-1) since the output is always 19 chars :)

i128 commented 6 years ago

eh scratch that, looks like column length is variable ...

ccammilleri commented 6 years ago

bah, the split is on ': ' so i didnt think this would happen...so hackerish of me. I got a better approach that will land in 0.7.3-beta

i128 commented 6 years ago

This issue is already resolved in v0.7.3-beta (you'll need to upgrade your hashview/agents too if you're using them)