Great news! It was at times an infuriating quest, but I finally got bkhive and samdump2 to work correctly, so thanks 2901119 for that lead! If anyone is still feeling generous though, john the ripper has got me stuck. I'm trying to crack these "dumps" with it. (For the sake of exactness, the file "samtext" is samdump2's output piped into plaintext form. )
When I simply type the command and directory
Code:
john '/media/(really long BT5 partition name)/pentest/SAMS/samtext'
john returns the message
Code:
fopen: john.ini: No such file or directory
so I looked in john's directory, and john.ini really isn't there. john.conf is there however, and in the man page for john, I saw there is a "--config=FILE" option to "use FILE instead of john.conf of john.ini". To me, that said that john.ini and john.conf might be somehow interchangeable, so I took it up on its offer, and wrote:
Code:
john --config='/pentest/passwords/john/john.conf' --format=LM '/media/(really long BT5 partition name)/pentest/SAMS/samtext'
and received the error :
Code:
Loaded 3 password hashes with no different salts (LM DES [128/128 BS SSE2])
fopen: password.lst: No such file or directory
I also tried the same line without "--format=LM" and received the same message. I then tried "--format=NT" for the hell of it, and again received a similar error:
Code:
Loaded 3 password hashes with no different salts (NT MD4 [128/128 SSE2 + 32/32])
fopen: password.lst: No such file or directory
I assume the 128/128 bit is something about salt length, maybe 128bit? But I really don't know much about that. I also gathered that john is trying to read from that wordlist it can't find, but I think i'd rather it just bruteforce the file if possible, even though it will probably take ages. If anyone knows how if or how it is possible to get john to bruteforce, that would be an hugely appreciated piece of information!
Thanks again to all of you who have taken time to help a bro triumph over ignorance!