![]() Multiple core support is provided by default. Installing libgmp3-dev was required in order to run multicore. The setup for multicore hashcat is pretty straight forward. However, on this occasion I was interested in experimenting and benchmarking with CPU only. Usually the GPU version of hashcat is the tool of choice for me when it comes to password cracking. John only shows the benchmarks of the algorithms it was compiled with (as far as i’m away). Both hashcat and john both have different benchmark outputs. The bench marks from this will differ depending on attack type, rules, and what hash type is being attacked, so take these results with a pinch of salt. If you need help setting up a box on AWS, there’s a getting started guide from amazon to get you going. I’ll be assuming you can reach the point of setup where you are logging into your freshly set-up machine on AWS (if you’re following along to set this up yourself). I used the Ubuntu Server 14.04 LTS image. ![]() In order to select the 36 core instance you’ll need to use a HVM (hardware virtual machine) enabled machine image. To get hashcat and john up and running with multi-core is a little fiddly (it’s not download and crack), so I thought I’d document the setup and show some benchmarks with hashcat and John the Ripper utilising 36 cores. As part of a project recently I got the chance to play with a 36 core instance on AWS (c4.8xlarge) for some password cracking related activities.
0 Comments
Leave a Reply. |