Hi.
I have an issue with importing keepass 1.x hashes. I created a test database with passphrase "test". I ran keepass2john on the .kdb file and i got this
test:$keepass$[hash removed by philsmd]*test
However, hashcat doesn't import the hash. What's the problem?
I did this because i noticed i have some old .kdb files that weren't imported, either in jtr or hashcat, and i extracted them all the same way with keepass2john. I even did it with the python script that was suggested in one of the previous threads ( https://gist.github.com/HarmJ0y/116fa1b5...4d7d367bbc ) and it's still not recognised. The files that aren't recognised all have this
*1*6000* and then some have *1*50000*
The hashes from kdbx database are recognised and can be ran with the same process. The databases are also not corrupted because i can open them with passphrase "test" in the keepass.
What's the issue and how to correct it? I use keepass2john from the jumbo patch john 1.8. I get "signature unmatched" when i use -m 13400 mode.
I have an issue with importing keepass 1.x hashes. I created a test database with passphrase "test". I ran keepass2john on the .kdb file and i got this
test:$keepass$[hash removed by philsmd]*test
However, hashcat doesn't import the hash. What's the problem?
I did this because i noticed i have some old .kdb files that weren't imported, either in jtr or hashcat, and i extracted them all the same way with keepass2john. I even did it with the python script that was suggested in one of the previous threads ( https://gist.github.com/HarmJ0y/116fa1b5...4d7d367bbc ) and it's still not recognised. The files that aren't recognised all have this
*1*6000* and then some have *1*50000*
The hashes from kdbx database are recognised and can be ran with the same process. The databases are also not corrupted because i can open them with passphrase "test" in the keepass.
What's the issue and how to correct it? I use keepass2john from the jumbo patch john 1.8. I get "signature unmatched" when i use -m 13400 mode.