ENHANCEMENT REQUEST - Hashcat running output

[ghost-ng]

Hello,

First off, love your tool; it offers a perfect mix of simplicity, security, and job control for hashcat over a web interface! I would like to make a suggestion: can you add a dropdown section within running sessions that displays the current hashcat output? The hashcat output provides % and time estimates that are very helpful in addition to the current increment count (for bruteforce). Hashcat also refreshed this screen if you press any key other than those mentioned on the screen.

Either way, still a great tool. Thank you for taking your time to create this project and make it open source!

UPDATE:
Apparently the session timed out...when I restored the screen it showed an integer overflow error...maybe I messed up the masked? All i wanted was a simple bruteforce mode attack so i manually (in the screen session) entered the -a -i --increment-min 10 --increment-max 10 -w 4 and the online session refreshed (which was cool!).

[sadreck]

Hi and thank you for the great feedback!

If I'm not mistaken what you're asking already exists if you click the "View Raw/Debug Information" button:

With regards to your update, the web gui already supports the --increment-min and --increment-max parameters, unless you were talking about adding -w? Also yes - as long as you use the same session hashcat name the GUI will pick it up regardless where it was started from. You can get the session name either from the "Raw Information" screenshot above (first line, "Session"), or by hovering your mouse over the session title:

Thanks,
Pavel

[ghost-ng]

yes this is great! My impatient self forgot all the procedures hashcat runs through before it starts cracking so I thought it was broken before it even started. Also i normally run hashcat without specifying a mask, so this tripped me up a little bit but I eventually figured it out.

I noticed that the when hashcat does error out, the "raw" dropdown doesnt populate; the process is already dead so maybe the engine is unable to pull up the output.

On the point about the -w option, this would be a great addition. I have found myself starting and stopping hashcat processes only to recover the screen and add the -w (3|4) to the command. Thanks for the responsiveness and again, great tool!

[sadreck]

Glad you got it sorted!

I'll have a look to implement the -w parameter along with fixing the blank error output.