cowpatty use GPU or will use it in future ?
acer 5920g , 345abg , nvidia 8600m
bt5 kde 64bit + acpi + cuda 4.0 / nvidia 270.40 / pyrit
You. Are. Doing. It. Wrong.
-Gitsnik
You are forgetting about the time it takes to pre-compute the table. It doesnt work like that. You dont seem to understand CUDA, it doesnt just "speed" up any old application. Its not steroids for all programs.
right, so , you can either use pyrit and pipe the hash's into cowpatty (which is already possible) , or you can completely rewrite and patch gempk (part of cowpatty , the hash generator) to compute the hash's and the use that hash table with cowpatty.
Seems silly to re-invent the wheel
You. Are. Doing. It. Wrong.
-Gitsnik
Wait. We're kinda going in circles now.
Let me ask you: How did you generate 'myhash' in your command above?
If you DON'T use pyrit and CUDA, it took you a long time.
If you DID use pyrit and CUDA, it took less time.
The cowpatty application takes 'myhash' as one of its INPUTS.
Pyrit and CUDA generated 'myhash' quickly, as its OUTPUT.
Ok, I'm done.
You. Are. Doing. It. Wrong.
-Gitsnik
acer 5920g , 345abg , nvidia 8600m
bt5 kde 64bit + acpi + cuda 4.0 / nvidia 270.40 / pyrit