+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Misc (https://hashcat.net/forum/forum-15.html)
+--- Forum: User Contributions (https://hashcat.net/forum/forum-25.html)
+--- Thread: cudaHashCat64 on AWS EC2 (/thread-4143.html)
Pages:
1
2
RE: cudaHashCat64 on AWS EC2 - heydonms - 05-19-2015
What no one seems to have mentioned here is that they can be run in parallel. Sure for the price of ~10 days of processing you could buy a card that is good for years, but if you need it urgently, amazon may have an advantage.
If you break the task down, you can run that entire 10 days worth of processing on a couple of hundred instances and have it finished in an hour. You can't achieve the same kind of flexibility with physical machine.
Long term physical hardware is the better investment, but if you have extremely bursty requirements, letting someone else deal with the machines might be the better option.
RE: cudaHashCat64 on AWS EC2 - szhairui - 04-01-2018
(03-02-2015, 06:35 PM)Radical_Ronin Wrote: Hey All,
Worked on a fun project and thought this may help someone else out who's looking for some serious hardware to crack on. Theres a couple of other guides out there but they are pretty out dated and some of the AMIs dont even work any more.
......
lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:03.0 VGA compatible controller: NVIDIA Corporation GK104GL [GRID K520] (rev a1)
00:1f.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01)
......
Hashtype: SHA512
Workload: 256 loops, 256 accel
Speed.GPU.#1.: 71354.4 kH/s
......
Thanks for your post.
But my problem is that my hacking speed is too slow.
Quote:PS E:\Dev\ .\hc.exe -m 1800 -b --optimized-kernel-enable
hashcat (v4.1.0) starting in benchmark mode...
Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 970, 1024/4096 MB allocatable, 13MCU
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Hashmode: 1800 - sha512crypt $6$, SHA512 (Unix) (Iterations: 5000)
Speed.Dev.#1.....: 75255 H/s (69.85ms) @ Accel:512 Loops:128 Thr:32 Vec:1
Started: Sun Apr 01 22:23:39 2018
Stopped: Sun Apr 01 22:23:48 2018
Is there any difference between cudaHashcat and Hashcat (v4,.1.0)?
RE: cudaHashCat64 on AWS EC2 - MrMeeseeks - 04-02-2018
Please don't necro/hijack old threads.
And there are a lot of differences. The biggest being that cuda is no longer being used by hashcat as we have standardized OpenCL.
The best thing you could do is to read through the change logs from the time hashcat went from cuda/ocl to current.
Also, I noticed you are comparing sha512 to sha512crypt, which are two different algorithms.