Closed vysecurity closed 7 years ago
Isolated bug to issue with hash size, vs column size in db. Working on fix.
Until the fix is pushed to master, you can try a workaround of modifying the mysql table manually:
mysql -u root -p <your password>
use hashview; #hashview_dev if running in dev
ALTER TABLE hashes MODIFY originalhash varchar(1024);
Fantastic :)
After review, I set the value and although the hashes upload now, after selecting the mode to be 13100, I get another internal server error.
You can refer to Mubix's guide here if you want a Krb5 hash to crack: https://room362.com/post/2016/kerberoast-pt3/
Issue should now be resolved.
Do a
git pull
To get the latest code, and then run the upgrade instructions found here:
https://github.com/hashview/hashview/wiki/Upgrading-Hashview
Still get Internal server error when running with krb5tgs hashes. Hashcat recognises the format with -m 13100 hashview doesn't.
Is there a guide anywhere to understanding the right file format to select? I'm assuming a krb5tgs is just $hash but it would be nice to have a lookup table or some guide to verify how hashview expects these.
Get 500 internal error when submitting KRB5 hashes. -m 13100