Pyrit on AWS - Revision history

Admin: /* Build Pyrit */

2015-08-02T18:59:00Z

Build Pyrit

← Older revision		Revision as of 18:59, 2 August 2015
Line 400:		Line 400:

	==Build Pyrit==		==Build Pyrit==

			Instructions on the [[Pyrit]] page

			==Build Pyrit CUDA==

	Instructions on the [[Pyrit]] page		Instructions on the [[Pyrit]] page

2015-08-02T18:54:53Z

Build John The Ripper

← Older revision		Revision as of 18:54, 2 August 2015
Line 404:		Line 404:

	==Build John The Ripper==		==Build John The Ripper==

			Download it

			Check it

			Extract it

			<pre>
			cd src
			make clean linux-x86-64-avx
			</pre>

			(Note that since we aren't using John the Ripper as the password cracker, but only as a passthrough filter for wordlist generation, we don't need to worry about whether JtR will use our NVIDIA drivers.)

2015-08-02T18:53:23Z

Building Pyrit

← Older revision		Revision as of 18:53, 2 August 2015
Line 397:		Line 397:
	8 GB SSD is the root directory, mount point <code>/</code>, so that's how much you have "on-board," but the 60 GB xvdb, well, I guess that's cloud storage.		8 GB SSD is the root directory, mount point <code>/</code>, so that's how much you have "on-board," but the 60 GB xvdb, well, I guess that's cloud storage.

	=~~Building~~ Pyrit=		=Build Stuff=

			==Build Pyrit==

			Instructions on the [[Pyrit]] page

			==Build John The Ripper==

2015-08-02T18:41:25Z

GPU Info

← Older revision		Revision as of 18:41, 2 August 2015
Line 375:		Line 375:

	</pre>		</pre>


			==Hard Disks==

			I was hoping that once I logged onto the node, it would clear up some of the confusion about what I was seeing with the hard drive selection, 8 GB vs the advertised 60 GB. Turns out it is both:

			<pre>
			$ df -h

			Filesystem Size Used Avail Use% Mounted on
			/dev/xvda1 7.8G 782M 6.6G 11% /
			none 4.0K 0 4.0K 0% /sys/fs/cgroup
			udev 7.4G 12K 7.4G 1% /dev
			tmpfs 1.5G 332K 1.5G 1% /run
			none 5.0M 0 5.0M 0% /run/lock
			none 7.4G 0 7.4G 0% /run/shm
			none 100M 0 100M 0% /run/user
			/dev/xvdb 64G 52M 61G 1% /mnt
			</pre>

			8 GB SSD is the root directory, mount point <code>/</code>, so that's how much you have "on-board," but the 60 GB xvdb, well, I guess that's cloud storage.

	=Building Pyrit=		=Building Pyrit=

2015-08-02T18:39:18Z

Processors

@@ Line 333: / Line 333: @@
 address sizes	: 46 bits physical, 48 bits virtual
 power management:
 </pre>
 =Building Pyrit=

2015-08-02T18:34:56Z

2015-08-02T18:31:43Z

Getting GPU Instance

← Older revision		Revision as of 18:31, 2 August 2015
Line 84:		Line 84:
	We're finally done setting everything up in AWS, we're ready to grab our $2 GPU node.		We're finally done setting everything up in AWS, we're ready to grab our $2 GPU node.

	=Getting GPU Instance=		=Getting the GPU Instance=

	Okay, ~~now its time~~ to oggle at all the things on offer at the AWS store.		Okay, you're almost ready to oggle at all the things on offer at the AWS store. First you have to log out of AWS (I mean really log out) and then go to the log in page. When you enter your AWS account name, there should be a text link below that says something like "Log in as root". You'll need to do this to log in as root.

			Note that even if you use IAM to create a user named "root," it is essentially no different from any other account.

	==Operating System==		==Operating System==
Line 113:		Line 115:

	Once you click the Launch button, you have to pick how you're going to connect to the instance - what security keys you're going to use. I picked "Choose an existing pair" and picked the pair of keys that I had already set up.		Once you click the Launch button, you have to pick how you're going to connect to the instance - what security keys you're going to use. I picked "Choose an existing pair" and picked the pair of keys that I had already set up.

			=Log In=

			Once you've got your instance, you can log in to the machine. Find your private key, and in the AWS panel

2015-08-02T18:24:36Z

Hardware

← Older revision		Revision as of 18:24, 2 August 2015
Line 95:		Line 95:

	Your second choice is hardware. You can use the drop down menu to find GPU instances. There were two available to me: a GPU cluster with 8 CPU cores, 60 GB memory, and 16 GB RAM, or a monster 32 CPU core machine with 60 GB, 240 GB SSD storage, and a 10 Gigabit network link. Woah. That's serious.		Your second choice is hardware. You can use the drop down menu to find GPU instances. There were two available to me: a GPU cluster with 8 CPU cores, 60 GB memory, and 16 GB RAM, or a monster 32 CPU core machine with 60 GB, 240 GB SSD storage, and a 10 Gigabit network link. Woah. That's serious.

			I picked the "low end" GPU machine and kept going.

			==Configuring Instance==

			Settings related to the instance.

			==Adding Storage==

			This is where I got confused. On the Hardware page, the specs list a 60 GB hard drive. But here, the hard drive is 8 GB. What gives?

			==Configure and Security==

			Now you have the option of creating a new security group or using an existing one. I picked teh security group I already created, which had SSH, HTTP, and HTTPS enabled.

			==Launch, and More Key Pairs==

			Once you click the Launch button, you have to pick how you're going to connect to the instance - what security keys you're going to use. I picked "Choose an existing pair" and picked the pair of keys that I had already set up.

2015-08-02T09:29:28Z

What This Is All About

← Older revision		Revision as of 09:29, 2 August 2015
Line 7:		Line 7:
	AWS is Amazon Web Services, the rent-a-supercomputer marketplace. You can rent all kinds of computers, but most interesting for our purposes, you can rent a GPU cluster.		AWS is Amazon Web Services, the rent-a-supercomputer marketplace. You can rent all kinds of computers, but most interesting for our purposes, you can rent a GPU cluster.

	~~==AWS==~~		A helpful guide here: http://j0k3rrr.blogspot.com/2011/07/wpa-cracking-on-amazons-ec2-instance.html



	=How To Do It=		=How To Do It=

2015-08-02T09:02:17Z

Create Virtual Private Cloud

← Older revision		Revision as of 09:02, 2 August 2015
Line 73:		Line 73:

	Whew! Almost done. Now you have to determine if you have a Virtual Private Cloud (VPC) by default. When I logged into my AWS account, and opened the EC2 portal, I saw "VPC" in the upper right hand part of the page.		Whew! Almost done. Now you have to determine if you have a Virtual Private Cloud (VPC) by default. When I logged into my AWS account, and opened the EC2 portal, I saw "VPC" in the upper right hand part of the page.

			==Create Security Group==

			Now you have to create a security group that can access the node you're renting. Add access to port 22 for SSH. This allows your user account to access the nodes through port 22.

			It will also be useful to have HTTP and HTTPS traffic turned on, so add those too.

			That'll open ports 22, 80, and 443 on our AWS node.

			==Finally DONE==

			We're finally done setting everything up in AWS, we're ready to grab our $2 GPU node.

			=Getting GPU Instance=

			Okay, now its time to oggle at all the things on offer at the AWS store.

			==Operating System==

			Your first choice is operating system. I went with Ubuntu - classic - nothing fancy. We'll install everything we need from source.

			==Hardware==

			Your second choice is hardware. You can use the drop down menu to find GPU instances. There were two available to me: a GPU cluster with 8 CPU cores, 60 GB memory, and 16 GB RAM, or a monster 32 CPU core machine with 60 GB, 240 GB SSD storage, and a 10 Gigabit network link. Woah. That's serious.