How to setup Pyrit in EC2

A video has been posted on SecurityTube that shows in detail how to create a GPU-node in Amazon’s EC2 cloud and get Pyrit installed and running there. The measured performance of the node (defined by it’s type == $$$ you are willing to pay per hour of runtime) is around 50.000 PMKs per second. That’s not very high but not bad either. The point is that you can setup and run (== pay) and shutdown (== not pay) the node anytime you like – there is no fixed cost for hardware. If you want more performance per second, you pay more per second.
The video is about one hour long so there should be only little room for uncertainties.



  1. would it be possible to start a client and 19 server instances or is it not possible to communicate between the instances?

    • That is possible in EC2. It’s probably more reliable to split the workload between the nodes and let them run on their own. Otherwise you pay for the traffic between them. Remember that 50k PMKs per second is roughly equivalent of 1.5 megabytes per second.

      • So it would be better to split the wordlist into 20 parts and give every instance another?

      • If these parts are large, e.g. supply work for at least some minutes / hours.

    • When I tested this back when the GPU clusters first became available, I ended up seeing about 50k PMK/s on the first (main) instance and then only around 17k PMK/s on the rest of the instances. Didn’t put too much work into tweaking it though since i was getting more than that on my desktop machine for cheaper (free).

Comments RSS TrackBack Identifier URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

  • RSS Unknown Feed

    • An error has occurred; the feed is probably down. Try again later.