How to take all the power of Elcomsoft Distributed Password Recovery (cuda+cpu)

If you use EDPR, when you try to crack a cuda capable thing, EDRP only use the GPU instead GPU+CPU. But, there is a trick to use both. It’s quite simple, you only need to install a virtual machine, then install EDRP into vm.

Diferences? well, with gpu, speed cracking for LM was 22.5M/s, but after vm, it increases to 28.6M/s.

One screenshot.

EDRP GPU+cpu

EDRP GPU+cpu

Comments (4)

Benchmark LM Cracking – CPU vs. GPU – John the Ripper vs. Cain vs. Elcomsoft Distributed Password Recovery

Hi to all. This is my firs post in english (I’m not the best writing in english).

I made a Benchmark for LM Cracking using my laptop:

Dell XPS M1530
Intel Core 2 Duo T7500 2.2Ghz
4 GB RAM
Windows Vista Ultimate
Hard Disk 120 GB 7200 RPM
Nvidia Gforce 8600M GT 256 MB

I Used:

  • John The Ripper (386 and mmx)
  • Cain
  • Elcomsoft Distributed Password Recovery

BENCHMAR

The objetive was test how many password/seg could be cracked using diferent software.
There are crackers based in cpu and recently in gpu.
For CPU test, I used John the ripper (386 and mmx) and CAIN.
For GPU test, I used Elcomsoft Distributed Password Recovery. Although this software allow more than 1 cliente, I only used my own laptop.

Here we go.

JOHN THE RIPPER 386. Speed: 4 M/s

John the ripper 386 test in core 2 duo 2.2GHZ

John the ripper 386 test in core 2 duo 2.2GHZ

JOHN THE RIPPER MMX. Speed: 9.2 M/s

John the ripper mmx test in core 2 duo 2.2 Ghz

John the ripper mmx test in core 2 duo 2.2 Ghz

CAIN. Speed: ~8 M/s

Cain cracking LM hash in core 2 duo 2.2 Ghz

Cain cracking LM hash in core 2 duo 2.2 Ghz

ELCOMSOFT DISTRIBUTED PASSWORD RECOVERY (GPU). Speed: 22.5 M/s

Elcomsoft Distributed Password Recover with 1 GPU cracking at 22.5 M/s

Elcomsoft Distributed Password Recover with 1 GPU cracking at 22.5 M/s

FULL RESULTS

EDPR (gpu):            22572914 c/s
John mmx (cpu):       9230000 c/s
Cain (cpu):                7969348 c/s
John 386 (cpu):         4043000 c/s

Lm Cracking Benchmark

Lm Cracking Benchmark

Comments (3)