Cryptohaze.com

Let's try this out.

GRTCrack-CPP has a tendency of segfaulting. I've left debug symbols in it. Please, if you can reproduce a segfault, run it in gdb and get me the stack trace/failure points! I can't reproduce it reliably.


THERE ARE COMMAND LINE DIFFERENCES!

GRTMerge now takes the "-m" argument to tell it how many megabytes to use. This should be roughly half your RAM, since it actually uses a ton more. It's a lot faster than the old one, but generates slightly different output. Still an open issue I'm working on...

GRTCrack is the big set of changes.

It now takes, instead of the "-s [hash]" argument, a "-f [hashfile]" argument.

The hashfile is a standard newline separated hash file.

It also right now ONLY SUPPORTS MD5 len 6-10. If it claims to do some other hash... it's lying. Seriously. MD5 ONLY! Still a work in progress, but I wanted to get it out there.

Feedback welcome!

//EDIT: Let's try this version out...

yay multi hash.

All i can say is nice and... FIRST

Great Job Bitweasel, but I get an CUDA error :

CUDA error in file "GRTCandidateHashesMD5.cu" in line 39 : invalid device symbol.

with the settings :

./GRTCrack-CPP -h MD5 -f test /output/*.grt

What GPU are you on? I'll take a look at that error tonight - I'm not around the source right now.

I tested it with a NVIDIA... 240GT
9800GT

That's a charset issue. What charset file were you using?

Post the full command line & I'll see if I can reproduce it.

I try it with this command line:

user@computername:~/Desktop/GRTCrack-Multi$ ./GRTCrack-CPP -h MD5 -f md5 GRT-MD5-len6-fullcharset-perfect/*.grt
Got 2 hashes!
Processing GRT file GRT-MD5-len6-fullcharset-perfect/MD5-idx1-chr95-cl100000-perfect.grt

Table version: 1
Hash: MD5
Password length: 6
Table index: 1
Chain length: 100000
Num chains: 9915810
Perfect table: Yes
Charset length: 95
Charset: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQR
STUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~

Elements: 2
Elements per unit: 1
Number of workunits: 2
WU init complete
Cuda error in file 'GRTCandidateHashesMD5.cu' in line 39 : invalid device symbol.

Weird.

What GPU are you using? And can you try it after a reboot in case the GPU memory is fragmented?

I tried it with a NVIDIA 240GT, a 9800GT and different tables (own creation) but same result.
The other GRT-Tools don't make any toubles.

Damn.

Alright, probably something stupid I'm doing with memory. I've got a block of time this weekend set out to sit down with valgrind, hopefully it'll fix it.