Shearing FireSheep with the Cloud

 
If your laptop ever connects to a network behind enemy lines (e.g. hhonors, attwifi, panera), this post is for you. The step-by-step directions below allow you to stand up a portable, cloud-based private VPN that you can use from anywhere – for around $0.50 a month. Once you get everything setup, you can feel good connecting to a hotspot and laugh at the guy running FireSheep.

 

Speaking of Firesheep, I’ve actually had some people close to me (including my wife) ask how they can prevent these types of attacks from happening. There are some nice “off-the-shelf” solutions like HTTPS Everywhere and BlackSheep but as a security professional I wanted to give a recommendation that would provide broader coverage than these solutions.

 

Enter Amazon’s recently introduced Free Tier for EC2. I’ll save my thoughts and comments on “The Cloud” and security for a later date (and after a couple of beers), but for the purposes of this solution, it works great to help you increase your security while using open wireless networks. Quite simply, the solution I came up with was to create an EC2 instance with Ubuntu 10.04 LTS server and setup OpenVPN and SideStep. This allows me to route all of my traffic over an SSL or SSH VPN to my EC2 instance and then out to the Internet.

 

To graphically represent what this solution offers, below is a picture of your laptop while surfing on an Open Wi-Fi network such as those at Starbucks.

Your Laptop @ Starbucks

The second image is the guy running Firesheep at Starbucks.

The Guy @ Starbucks Running FireSheep

The last image depicts your laptop running OpenVPN or SideStep at Starbucks.

Your Laptop Armed with OpenVPN or SideStep @ Starbucks

Enough with the ‘Behind Enemy Lines’ comparisons…I swear. I installed other services on my EC2 instance, like Privoxy and iodine (see my post on tunneling traffic via iodine), but for the purpose of this post, I will limit the scope to creating an EC2 instance, installing and configuring OpenVPN, and installing and configuring SideStep.

 

A couple of notes before we get started. While the instructions that follow utilize Amazon’s Free Tier, this setup will cost you roughly $.50 per month. There are ways to shrink your EC2 ami to fit within the Free Tier’s EBS limit of 10GB, but I will pay around $.50 a month to have this service available to me (the Ubuntu AMI we will use utilizes 15GB of EBS). Thanks to Martin’s post in the comments below, I have updated this post to utilize an 8GB ami, which is less than the 10GB allotted in the free tier for EBS storage.

 

 

So let’s get started…

 

1. If you haven’t already, head over to Amazon EC2 and create an Amazon EC2 account.

 

2. Once you have created an account, visit the AWS Management Console and click on the ‘Key Pairs’ link on the left side of the screen. Here you will create a Key Pair that will allow you to login to your EC2 instances. Click on the ‘Create Key Pair’ button and name the Key Pair something unique. I chose ‘JustinsAllEC2Key’. Save the file in your ~/Download folders and move it to your ~/.ssh/ folder by issuing the following commands:

 

Your Mac
jmorehouse@Old-Trafford:~$ cd Downloads
jmorehouse@Old-Trafford:Downloads$ mv JustinsAllEC2Key.pem ~/.ssh/
jmorehouse@Old-Trafford:Downloads$ chmod 400 ~/.ssh/JustinsAllEC2Key.pem

 

3. Now that you have a key pair, it is time to create and launch an instance. Click on the ‘AMIs’ link on the left side. Then select All Images from the ‘Viewing’ drop-down (it takes a minute to load all of the available instances), and search for ami-4a0df923 ‘ami-3e02f257’. This is an EBS instance of Ubuntu 10.04 LTS Server 64-bit 32-bit from Alestic. EBS allows for persistent storage, so that your setting will remain even when you power-cycle your instance.

 

4. Select the AMI and then click the ‘Launch’ button at the top. You will be prompted with a number of options, and I recommend using the following:
  • Number of Instances: 1
  • Availability Zone: No Preference
  • Instance Type: Micro
  • Launch Instances
  • Click ‘Continue’

 

  • Kernel ID: Default
  • RAM Disk ID: Default
  • No Monitoring
  • No User Data
  • Click ‘Continue’

 

  • Key = ‘Name’
  • Value = ‘Free Tier EC2 Ubuntu 10.04 Instance’
  • Click ‘Continue’

 

  • Choose from your existing Key Pairs – ‘JustinsAllEC2Key’ -> This is the key you previously created in Step 2 and moved to your ~/.ssh/ folder.
  • Create a new Security Group – ‘InternetAccessible’ -> This akin to a firewall ruleset group. I created a new once called ‘InternetAccessible’, but you can just as simply use and edit the ‘Default’ group.
  • Describe your security group – ‘Services allowed from the Internet’
  • Select ‘SSH’ from the drop-down ‘Applications’ menu -> I left ‘All Internet’ as we want to access this instance from wherever we are on the Internet.
  • Click ‘Add Rule’
  • Select ‘HTTPS’ from the drop-down ‘Applications’ menu -> This will give us access to our OpenVPN server. I also left this open to ‘All Internet’ for the same reason we configured SSH this way.
  • Click ‘Add Rule’
  • Click ‘Continue’

 

5. You are then be presented with a confirmation page where you should confirm your setting and make any necessary changes. If everything looks good, go ahead and launch your instance.

 

6. Your instance is now launching. Click on the ‘View your instances on the Instances page’ link to access information about your instance.

 

7. Now we will assign a static IP address to your instance as Amazon makes this feature available for free (what IPv4 shortage?). Click on the ‘Elastic IPs’ link on the left side. Then click on the ‘Allocate New Address’ button in the center of the page. Click the ‘Yes, Allocate’ button, and then click the checkbox infront of the newly added IP address. We want to associate this IP with your newly created instance. You can do this by now clicking on the ‘Associate’ button at the top. Select the ‘Instance ID’ for the instance you just created (there should be only one Instance ID in the drop-down) and click ‘Associate’. Copy the IP address somewhere handy as we will need it in a couple of minutes.

 

8. Once you have done this, it’s time to login to your EC2 instance! You can perform this from Terminal using the following:

 

Your Mac
jmorehouse@Old-Trafford:Downloads$ cd ~
jmorehouse@Old-Trafford:~$ ssh -i ~/.ssh/<filename>.pem ubuntu@IPAddress

 

9. Type ‘yes’ to accept the RSA key fingerprint and you should see something akin to the following:

Linux ec2 2.6.32-309-ec2 #18-Ubuntu SMP Mon Oct 18 21:00:50 UTC 2010 x86_64 GNU/Linux
Ubuntu 10.04.1 LTS

Welcome to Ubuntu!
* Documentation: https://help.ubuntu.com/

System information as of Fri Dec 3 00:40:20 UTC 2010

System load: 0.0 Processes: 60
Usage of /: 6.2% of 14.76GB Users logged in: 1
Memory usage: 6% IP address for eth0: 10.XX.XX.XX
Swap usage: 0% IP address for tun0: 10.X.XX.X

Graph this data and manage this system at https://landscape.canonical.com/
———————————————————————
At the moment, only the core of the system is installed. To tune the
system to your needs, you can choose to install one or more
predefined collections of software by running the following
command:

sudo tasksel –section server
———————————————————————

14 packages can be updated.
4 updates are security updates.

Last login: Thu Dec 2 23:22:38 2010 from pool-XX-XX-XX-X.domain.net

10. At this point you want to perform some hardening and maintenance on the box.

 

Update passwords
EC2 Instance
ubuntu@ec2:~$ sudo su -
ubuntu@ec2:~$ passwd ubuntu

(Enter in a new password for the ‘ubuntu’ account. This is the default account on your EC2 instance. I recommend storing these passwords in KeePassX)

ubuntu@ec2:~$ passwd

(Enter in a new password for the ‘root’ account. This account should be need no explanation.)

 

Update packages
EC2 Instance
ubuntu@ec2:~$ exit
ubuntu@ec2:~$ sudo apt-get update

(This updates the list of known packages.)

ubuntu@ec2:~$ sudo apt-get upgrade -y

(This upgrades the installed packages to their latest version.)

 

If you are prompted for grub-pc config update, just hit enter. Also select ‘Yes’ at the next Grub message window.

 

Time Zone
EC2 Instance
ubuntu@ec2:~$ sudo dpkg-reconfigure tzdata

 

Follow the instructions to setup the proper timezone information for your EC2 instance.

 

ubuntu@ec2:~$ sudo reboot now

(This will reboot the sytem. Wait about 2 minutes before you try and reconnect to the EC2 instance via Terminal using the above ssh command.)

 

11. At this point I setup a host record for my EC2 instance so that I could use DNS to access it. I also configured the hostname on the system to match the DNS record. This is an optional step, and if you aren’t sure what I am talking about or aren’t sure how to do it, don’t worry about it.

 

12. Now that we have our EC2 instance configured and ready to go, it is time to install and configure OpenVPN. To install OpenVPN on your EC2 instance, simply type the following from within your SSH session:

 

EC2 Instance
ubuntu@ec2:~$ sudo apt-get -y install openvpn libssl-dev openssl

 

13. Now we need to create the certificates to use with OpenVPN. First let’s copy the easy-rsa tool to the OpenVPN folder.

 

EC2 Instance
ubuntu@ec2:~$ cd /etc/openvpn/
ubuntu@ec2:/etc/openvpn$ sudo mkdir easy-rsa
ubuntu@ec2:/etc/openvpn$ sudo cp -r /usr/share/doc/openvpn/examples/easy-rsa/2.0/* /etc/openvpn/easy-rsa/
ubuntu@ec2:/etc/openvpn$ sudo chown -R $USER /etc/openvpn/easy-rsa/
ubuntu@ec2:/etc/openvpn$ cd /etc/openvpn/easy-rsa/

 

14. We now need to edit the ‘vars’ file to provide some information for our SSL certificates. You will need to know how to use the ‘vi’ text editor. If you don’t know how to use it, I recommend this tutorial.

 

EC2 Instance
ubuntu@ec2:/etc/openvpn/easy-rsa$ sudo vi vars

 

Change export ‘KEY_SIZE=1024’ to ‘export KEY_SIZE=2048’
Change export KEY_COUNTRY=”US” to your country.
Change export KEY_PROVINCE=”CA” to your state. I.e. ‘KEY_PROVINCE=”FL”‘
Change export KEY_CITY=”SanFrancisco” to your city. I.e. ‘KEY_CITY=”Tampa”‘
Change export KEY_ORG=”Fort-Funston” to your organization or something else. I did my family (‘KEY_ORG:”Morehouse-Family”‘)
Change export KEY_EMAIL=”me@myhost.mydomain” to your email address.

 

Save the file by hitting the ‘ESC’ key and then typing ‘:wq’ and press enter.

 

ubuntu@ec2:/etc/openvpn/easy-rsa$ source vars
ubuntu@ec2:/etc/openvpn/easy-rsa$ ./clean-all
ubuntu@ec2:/etc/openvpn/easy-rsa$ source vars
ubuntu@ec2:/etc/openvpn/easy-rsa$ ./build-ca

 

You should be prompted for the following. You can hit ‘enter’ to keep the default value you already setup by editing the ‘vars’ file.

 

Country Name (2 letter code) [US]:
State or Province Name (full name) [FL]:
Locality Name (eg, city) [Tampa]:
Organization Name (eg, company) [Morehouse-Family]:
Organizational Unit Name (eg, section) []:Personal
Common Name (eg, your name or your server’s hostname) [justin.domain.org]: -> Enter your hostname here if you created a DNS record. Otherwise enter your EC2’s Elastic IP address from Step 7.
Name []:Justin Morehouse
Email Address [justin@mydomain.com]:

 

Now execute the following commands:

 

ubuntu@ec2:/etc/openvpn/easy-rsa$ ./build-dh

(This takes some time. Like 2 minutes.)

ubuntu@ec2:/etc/openvpn/easy-rsa$ source vars
ubuntu@ec2:/etc/openvpn/easy-rsa$ ./pkitool --server server
ubuntu@ec2:/etc/openvpn/easy-rsa$ cd keys
ubuntu@ec2:/etc/openvpn/easy-rsa/keys$ openvpn --genkey --secret ta.key
ubuntu@ec2:/etc/openvpn/easy-rsa/keys$ sudo cp server.crt server.key ca.crt dh2048.pem ta.key /etc/openvpn/

 

15. Now we have created the CA and Server certificates. Now we need to create keys for our users. For the purpose of this blog, we will create one key for one user. You can repeat this step for each additional user you wish to allow to access your OpenVPN server.

 

EC2 Instance
ubuntu@ec2:/etc/openvpn/easy-rsa/keys$ cd..
ubuntu@ec2:/etc/openvpn/easy-rsa$ source vars
ubuntu@ec2:/etc/openvpn/easy-rsa$ ./pkitool <yourname>

(I typed ‘./pkitool justin’)

ubuntu@ec2:/etc/openvpn/easy-rsa$ cd ..

 

16. Now we need to create an archive to download all of the necessary files from the server to the system you want to configure to use OpenVPN (Your laptop). I recommend using Cyberduck to access the .tar file we create. Remember to use your EC2 key to login with Cyberduck. It is the key we created in Step 2 and stored in your ~/.ssh/ folder (JustinsAllEC2Key.pem). Remember, the keys.tar file will be located in the /etc/openvpn/ directory. Download the keys.tar file to your Downloads directory.

 

EC2 Instance
ubuntu@ec2:/etc/openvpn$ sudo tar czf keys.tgz ca.crt ta.key easy-rsa/keys/<em>yourname.crt</em> easy-rsa/keys/<em>yourname.key</em>

 

17. Now it’s time to configure your OpenVPN server. You can most likely use the pre-configured template I posted online. It uses the IP address scheme of 10.8.80.0/24 for VPN clients, so unless you are using that network somewhere else, you don’t need to change a thing in the configuration. If you do need to edit the network, you can download the server.conf file here or issue the commands below and use vi to edit it as you would like. Use the commands below to download the server.conf file to the /etc/openvpn folder on your EC2 instance.

 

EC2 Instance
ubuntu@ec2:/etc/openvpn$ sudo wget http://stratumsecurity.com/wp-content/uploads/server.conf

 

18. Now we have to setup ip forwarding on your EC2 instance. We’ll use sudo to perform these commands.

 

EC2 Instance
ubuntu@ec2:~$ sudo su -
root@ec2:~$ modprobe iptable_nat
root@ec2:~$ echo 1 &gt; /proc/sys/net/ipv4/ip_forward
root@ec2:~$ iptables -t nat -A POSTROUTING -s 10.8.80.0/24 -o eth0 -j MASQUERADE
root@ec2:~$ iptables-save &gt; /etc/iptables.conf
root@ec2:~$ echo '#!/bin/sh' &gt; /etc/network/if-up.d/iptables
root@ec2:~$ echo "iptables-restore &lt; /etc/iptables.conf" &gt;&gt; /etc/network/if-up.d/iptables
root@ec2:~$ chmod +x /etc/network/if-up.d/iptables
root@ec2:~$ echo "net.ipv4.ip_forward=1" &gt;&gt; /etc/sysctl.conf
root@ec2:~$ reboot now

 

19. Back on your Mac, download and install Tunnelblick. It is is a free, open source Graphic User Interface (GUI) for OpenVPN on Mac OS X. You can download the latest stable version from here.

 

20. Once you have installed Tunnel blick, go do your ‘Downloads’ folder and extract your keys.tar files. Copy the ca.crt, ta.key, <yourname>.crt, and <yourname.key> files from the extracted .tar file to the Tunnelblick directory located at ‘~/Library/Application\ Support/Tunnelblick/Configurations/‘. (<yourname>.crt and <yourname.key> will be in the ‘easy-rsa/keys’ folder. Make sure all of the extracted files are in the ‘~/Library/Application\ Support/Tunnelblick/Configurations/‘ folder!)

 

21. You will now need to edit the client template that I have posted here. Download the file to ‘~/Library/Application\ Support/Tunnelblick/Configurations/‘ and edit the following three items:
  • Line 42: Change ‘<IP or hostname>’ to your EC2 instance’s IP address, from Step 7, or the DNS name you gave it.
  • Lines 89 & 90: Change cert <yourname>.crt & key <yourname>.key to the names of the .crt and .key files you extracted from the keys.tar file. This the client certificate you created for yourself in Step 15.
22. Once this is done, open up a web browser and go to IP Chicken. Obesrve your current source IP address. Then open Tunnelblick and from the menu bar at the top, select Connect ‘ec2’. Reload your browser and notice that you now have a source IP address of your EC2 instance! Congratulations on getting OpenVPN on an EC2 instance setup. Now let’s setup SideStep.

 

23. While Tunnelblick allows you to create an on-demand SSL tunnel to proxy all of your network traffic through your EC2 instance (for both wired and wireless) networks, SideStep takes the guess work out of when to use a proxy to secure your network when you are on an open wireless network (it currently only works on wireless networks, but Chetan is going add the capability to use it on an wired network as well). First download and install SideStep.

 

24. SideStep uses passwords or keys to create an on-demand SSH tunnel that proxies your traffic. As our EC2 instance doesn’t allow for password logins via SSH, we need to create a new keypair to use with SideStep. Using Terminal on your Mac, issue the following commands:

 

Your Mac
jmorehouse@Old-Trafford:~$ cd ~
jmorehouse@Old-Trafford:~$ ssh-keygen -t rsa -f ~/.ssh/id_ec2

 

Enter in a passphrase twice, and store it some place safe (KeePassX) because you will need it later.

 

jmorehouse@Old-Trafford:~$ scp -i .ssh/JustinsAllEC2Key.pem .ssh/id_ec2.pub ubuntu@IP:~/.ssh/

(Key created in Step 2 and IP address from Step 7.)

 

25. Still within Terminal, log back into your EC2 instance and append the public key to your authorized_keys file.

 

Your Mac
jmorehouse@Old-Trafford:~$ cd ~
jmorehouse@Old-Trafford:~$ ssh -i ~/.ssh/&lt;filename&gt;.pem ubuntu@IPAddress

(Key created in Step 2 and IP address from Step 7.)

 

EC2 Instance
ubuntu@ec2:~$ cd .ssh/
ubuntu@ec2:~/.ssh/$ cat &gt;&gt; authorized_keys id_ec2.pub
ubuntu@ec2:~/.ssh/$ chmod 640 authorized_keys
ubuntu@ec2:~/.ssh/$ exit

 

26. Now we need OSX to prompt us for the passphrase for the id_ec2 key, so from Terminal, enter the following:

 

Your Mac
jmorehouse@Old-Trafford:~$ cd ~
jmorehouse@Old-Trafford:~$ ssh -i .ssh/id_ec2 ubuntu@IP

 

You should be prompted for a password. Check the save the password to your Key Chain and hit ok. You should now have an SSH session to your EC2 box using your new key. You can go ahead and exit from your SSH session and close out all of your Terminal sessions and quit the Terminal application.

 

27. Now fire up SideStep and click the ‘Next’ button. Under ‘I already have one’ enter ‘ubuntu’ as the Username, your IP address from Step 7 as the hostname, and press ‘Test Connection to Server.’ You should receive a ‘Connection to server succeeded!’ message. Now click the ‘Next’ button. Read the notes and check the box that reads ‘Run SideStep on login.’ Click ‘Finish.’

 

28. SideStep is now on the menu bar next to Tunnelblick. I added Tunnelblick to my login items so that it is launched when I boot. Understand the differences between these two tools (Tunnelblick and SideStep) and when to use each.

 

Congratulations! If you made it this far, pat yourself on the back. This was a long tutorial, but it should work if you followed each step. If you have any problems, hit me up on Twitter (@Mascasa).

 

Enjoy surfing open wireless networks or hostile wired network securely!

 

146 Comments

Andre December 27, 2010

@Justin Thank you for your great post. It took a while for me to get back to this. I did get it all to work and learned a lot about Unix in the process. Sometimes the best course of action is to start over rather than trying to find the needle in the hay stack. You can edit a read-only file with Vi as a super user – one of those ‘duh’ moments 😉

Reply
 
Ian Chilton January 25, 2011

@Trevor
Re your point 2 – I believe WPA provides inter-client-isolation – so using WPA should render Firesheep useless if both parties are on the wireless (in a cafe) for instance.

That said, it’s no substitute for a full VPN Solution.

Thanks Justin for providing such a great guide – this is pretty much identical to how i’ve been setting OpenVPN up for a while so it’s good to know i’m doing it correctly.

Reply
 
Ian Chilton January 25, 2011

@Philip Tomas
AFAIK there is no way to connect to OpenVPN from an iPhone – you would need an IPSec or PPTP vpn server for that.

Reply
 
Kat January 26, 2011

Thanks for this – you explain things really well for non-tech n00bs like me. I got as far as step 16, and I’m a bit stuck:

“Remember to use your EC2 key to login with Cyberduck. It is the key we created in Step 2 and stored in your ~/.ssh/ folder (JustinsAllEC2Key.pem). Remember, the keys.tar file will be located in the /etc/openvpn/ directory. Download the keys.tar file to your Downloads directory.”

I installed Cyberduck, but I’m a bit stuck on the part where I log in to my EC2 account. How do I access my key?

Reply
 
Roger January 30, 2011

Great solution. One question though: when selecting the fixed IP address, does Amazon make it possible to get UK allocated IP addresses? This would help me solve the problem of the wireless security, and also accessing “UK only” services.

Thanks

Reply
 
Martin February 7, 2011

Two things I’d like to point out in order to keep $ charges to a minimum, from my own experience:

1) Use a CNAME record instead of a A record to point to your Amazon EC2 Instance. If you use an A record, the EC2 instance will talk to itself using the external IP and get charged “$0.010 per GB – regional data transfer – in/out/between EC2 Avail Zones or when using public/elastic IP addresses or ELB”. Point your CNAME record to your ec2-xx-xx-xx-xx.compute-1.amazonaws.com address. More info: http://www.stevenringo.com/elastic-ip-on-amazon-ec2-why-using-a-cname-is-better-than-an-a-record/

2) Keep only 1 attached Elastic IP and 0 non-attached Elastic IPs. Non-attached Elastic IPs will be billed “$0.01 per non-attached Elastic IP address per complete hour”. In my attempt to capture a memorable Elastic IP address, I allocated the maximum number IPs (5 I believe) to decide between them. I associated my favorite IP to my instance but forgot to release the remaining 4 non-attached IPs and was billed by the hour for each of them I left overnight.

Although these $ charges are just pennies, and not a big deal, I thought it worthwhile to leave a warning here for those who truly want to keep a $0.00 balance

Reply
 
Martin February 7, 2011

I forgot one more thing.

3) Use a AMI that is under 10GB as you only get “10 GB of Amazon Elastic Block Storage, plus 1 million I/Os, 1 GB of snapshot storage, 10,000 snapshot Get Requests and 1,000 snapshot Put Requests” in the Free Tier for Amazon’s AWS.

the AMI used in this tutorial is ami-4a0df923 and uses 15GB. Amazon has updated their AMI’s to include under 10GB ones, recently. I personally used ami-3e02f257 which clocks in at 8GB.

Reply
 
Martin February 7, 2011

OK I keep remembering more things to write. Sorry about that…

If you’re accessing your EC2 Instance via ssh from a Windows machine using a SSH client such as PuTTY, then you have to convert the *.pem key into a format that PuTTY can use with PuTTYgen.

Open up PuTTYgen, hit the Load button, browse to your *.pem key saved earlier (select All Files if you have to, to see it) , a message will popup confirming what we imported and will give you further instructions. Click OK on that message, and hit “Save private key” as instructed.

Use the saved ppk file with “putty -i -l ubuntu” to login to your EC2 Instance.

Reply
 
Riaan February 13, 2011

Hi Justin,

Great tutorial, thanks very much for sharing it. I appreciate you’ve written this from a Mac user’s perspective, and on my Mac it works a treat. However I’ve tried to make it work on my Vista machine and have hit a slight snag.

The OpenVPN GUI connects without a problem and picks up a 10.8.80.x IP address. However traffic still routes over my wired connection, confirmed by IPChicken.

So I turned the firewall off for all connections (Windows Firewall), but this made no difference. IPconfig revealed the following for the OpenVPN (TAP) connection:

IPv4: 10.8.80.6
Subnet: 255.255.255.252
Gateway: MISSING
DHCP server: 10.8.80.5
DNS: 208.67.222.222 and 208.67.220.220

So I figured the missing gateway must be the issue, and manually configured it as 10.8.80.1 up to 5, none of which helped.

Ping tests reveal that the only 10.8.80.x IP address I’m able to ping is myself (.6).

Any suggestions on what these IP settings should be, or if there are some amendments to make in order to make it work on Vista?

Much appreciated,
Riaan

Reply
 
Riaan February 13, 2011

PS re the previous post: OpenVPN works fine on my XP machine, only Vista has issues.

Riaan

Reply
 
Sebastian February 18, 2011

Hi,

i followed your great tutorial in december and everything was working fine. Today i want to login with ssh ubuntu@ipadress and get an Permission denied (public key) error message.

i am not sure what to do now, hopefully you can help me out?!

Regards,
Sebastian

Reply
 
Sebastian February 18, 2011

Ok. Problem solved. I have used the wrong *.pem file. Everything works fine.

Regards,
Sebastian

Reply
 
Martin February 18, 2011

Riaan, I think this may help your situation, 1) try running OpenVPN GUI as an administrator and 2) add these two lines to your ovpn file:

route-method exe
route-delay 2

I was connected via OpenVPN GUI as well but my traffic wasn’t routing over the VPN connection for some reason as well. If you look in the log, you might see the following:

“ROUTE: route addition failed using CreateIpForwardEntry: One or more arguments are not correct. [if_index=18]”
and/or
“Route addition via IPAPI failed”

if that is the case, then those two lines should help you out. Just make sure to run OpenVPN GUI as an admin to mitigate any permissions problems in establishing the route.

That was the last problem I encountered in setting up everything, and forgot to post about it here. Hopefully the entirety of this article and our comments will help some strangers get on the internet, whether they are evading firesheep or circumventing censorship.

Reply
 
mrevil February 21, 2011

Thanks for the awesome tutorial, it was exactly what I was looking for.

Reply
 
Justin February 22, 2011

@Martin
Thanks! I just switched my personal ami to this image and will update the blog now!

Reply
 
David Beegle March 1, 2011

I am completely ignorant when it comes to Linux, SSH and using keyfiles so I am having trouble with step 16. I am supposed to download the tar file I created using CyberDuck (I have Transmit and have tried that as well) and can’t figure out how to use either CyberDuck or Transmit to get into the instance and download the tar file. Is there instructions for this anywhere?

Reply
 
David Beegle March 1, 2011

Never mind. Got my problem figured out with using Transmit. Thanks.

Reply
 
David Beegle March 1, 2011

Awesome! Got it working. This will be great. Thanks much for the walkthrough.

Reply
 
Alex March 11, 2011

Can anyone explain why I’m getting a permission denied. Followed the instructions, and on the first time trying to ssh in, i get this

The authenticity of host ‘xx.xx.xxx.xxx (xx.xx.xxx.xxx)’ can’t be established.
RSA key fingerprint is [fingerprint id].
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘xx.xx.xxx.xxx’ (RSA) to the list of known hosts.
Permission denied (publickey).

? I’m on OS X 10.6.6

Reply
 
Alex March 11, 2011

Ok, solved my problem. I has poor spelins 🙁

it’s ubuntu, not ubantu

Reply
 
Matthew Aaron McVickar March 14, 2011

I’m a little confused about how the bandwidth usage charges work. I regularly work long hours at a coffee shop, and would love to set this up for usage there, but if all of my outgoing bandwidth is routed through this EC2 instance, won’t I exceed the free limits very quickly?

Reply
 
Andrew March 14, 2011

Hi, I followed the tutorial above with no difficulties and my connection is now secured! However, I’ve already been charged 60 cents in the last 2 days by Amazon. Is this expected?

I’m not sure that I am eligible for the ‘free tier’ since I previously used Amazon S3 on my account about 2 years ago.

Reply
 
Justin March 14, 2011

@Matthew

For high bandwidth users, I would not recommend using EC2. It will cost you. You might want to look at Linode.com or even setting up an SSH tunnel to your house using SideStep.

Justin

Reply
 
Justin March 14, 2011

@Andrew,

What was the $.60 charged for?

Justin

Reply
 
Andrew March 14, 2011

So far, I’ve been charged $0.66 for 33 hours of $0.02 per Micro Instance (t1.micro) instance-hour (or partial hour).

(plus 5 cents for $0.10 per GB-month of provisioned storage 0.452 GB-Mo)

This has only been running since Saturday afternoon.

Reply
 
Justin March 14, 2011

@Andrew

I would contact Amazon and see if you are not signed up for the free tier.

Let me know.

Reply
 
Andrew March 14, 2011

Thanks.. I’ll try to get in touch with Amazon.

I think the problem might be that the free tier is limited to people who never used Amazon Web Services before the free-tier was announced. (unfortunately I played around with S3 about a year prior as an off-site backup solution.)

Reply
 
Paul March 15, 2011

@Andrew

I am in the same boat. I activated an S3 account for offsite backups like two years ago and I don’t think I used it once. Here is my response from AWS:

“Hello,

I’ve researched your account and see that your AWS account was created before October 21, 2010. Unfortunately, your account isn’t eligible for the AWS Free Usage Tier.

Please note that the definition of new customer as related to this offer is based on the creation date of your AWS account, and is not related to your current or previous use of AWS services.

Please review the full terms of this offer for more information:

http://aws.amazon.com/free/terms/

I’m sorry if this causes any disappointment. We hope to see you again soon.”

I suppose I could create a new account but if you read closely, it’s only free for the first year. They credit you 750 instance-hrs/mo (24 hrs/day) and 15 GB/mo, which is virtually unlimited data.

You have to remember to shut down the EC2 instance if you decide to keep it. As a frequent traveler with no desktop at home on which to host my own SSH setup, EC2 is still cheaper than most of the commercial solutions I’ve seen.

Reply
 
Percy March 16, 2011

I followed up to step 18 but can’t get Transmit or Cyberduck to connect to my EC2.

How else can I download the .tar file mentioned in step 20?
I even followed these steps (http://jeffreysambells.com/posts/2010/08/04/connecting-to-amazon-ec2-using-transmit/) to get it to work in Transmit.
No luck.

Could anyone help?

Thanks.

Reply
 
Justin March 17, 2011

@Percy

Do you have an outbound firewall? Perhaps on your mac or network?

Email me your IP and I will see if I can reach it -> http://scr.im/mascasa

Reply
 
bw March 17, 2011

am completely stuck on step 16! please help!!!

i can’t figure out how to use my EC2 key to login with Cyberduck – i’m sure it’s simple, but what am i missing?

Reply
 
Justin March 17, 2011

Check “Pubic Key Authentication” and then select your .pem EC2 key.

 
Percy March 17, 2011

@justin

I finished the tutorial. I was able to select the .pem in Transmit by copying it to the Desktop.
Thanks for your help!

Reply
 
PiersG March 20, 2011

Thanks for the guide, as others have said, a great introduction to AWS as well as a useful network facility to be able to access. During this week I’ll be changing all my machines over from SSH to OpenVPN.

As I’m in the UK I used the “EU West (Ireland)” AWS region and the “ami-fb9ca98f” image (8GiB ubuntu maverick 10.10) which worked flawlessly. I’ve changed the server.conf and OpenVPN client conf files to use UDP on port 1194.

Thanks again to Justin and all those submitting comments (eg use of PuTTY, CNAME etc). Very helpful!

Reply
 

[…] be usable in different situations where internet access is firewalled, but DNS queries are allowed.Shearing FireSheep with the Cloud | Stratum Security Blog – Quite simply, the solution I came up with was to create an EC2 instance with Ubuntu 10.04 […]

Reply
 
Lorin Rivers May 20, 2011

Thanks for the awesome guide. Might want to point out that in step 4, the default values for a given app (0.0.0.0/0) are in fact, any IP. Don’t know if the UI has changed since you initially wrote this or what, but I was mildly confused

Reply
 

[…] server hosting your website, your computer at home, or for about $0.50 / month, you can set up an Amazon EC2 Instance that can act as your proxy […]

Reply
 
Hormoz May 27, 2011

the tutorial is really helpful, thank you.
although I encountered an error at the end when Tunnelblick tries to connect, well it cannot connect, I posted its log here:
https://gist.github.com/991052
can someone help me on this ?

Reply
 
Justin May 27, 2011

@Hormoz it cannot find your hormoz.crt certificate file. Where did you place this file and what does your config file say for its path? Check them both.

 
Hormoz May 27, 2011

“hormoz.crt” is in “/etc/openvpn/easy-rsa/keys”; and in the .conf file I first just changed the name, & seeing its not working i wrote the whole address in there, that didn’t work either!

Reply
 
Shahid June 5, 2011

This was a fantastic tutorial. I managed to get everything working, which given the complexity of what is being described here, is a great testament to your clarity and quality of writing.

I couldn’t find the instance you were referring to, so I picked one that was reasonably close from the Alestic site – ami-2cc83145

I didn’t qualify for the free tier, so I’ve paid the extortionate (hehe) price of $0.44 for a day so far. 🙂 I don’t mind paying a few cents to protect each open session, but I probably wouldn’t spend around $10 a month for the privilege, given all the other hosting I’m paying for (Media Temple, BlueHost, NearlyFreeSpeech.net etc. etc.)

The cost of a micro instance is 2c an hour, and if you stop the instance, but keep the elastic IP, you still pay 1c an hour for the privilege, so that isn’t a fix either.

Is there a way around this? What would your advice be?

Once again, thanks – it was great to feel like a Unix guru for a few hours. 🙂

Reply
 
Shahid June 5, 2011

A quick update – I am now using Sidestep to connect via my MediaTemple server through SSH.

Is there any reason to keep my EC2 now? (I’ve also unloaded Tunnelblick, presumably I don’t need that any more as it was just a GUI for OpenVPN, which presumably I don’t need any more either?)

Finally – as a programmer, but not an Internet security or server expert (or even amateur), where should I go to learn the basics of some of the skills you’re illustrating in this article?

Many thanks for such an educational and well-written piece. You have a great teaching style.

Reply
 
Justin June 5, 2011

@Shahid

If you are using SideStep with MediaTemple, and you are ok with your DNS queries being sniffed on open networks, then you should be fine. I still keep my EC2 around if I need to try random things out, but I myself am using SideStep to my house for SSH-Proxy on open networks.

As for the blogs, LifeHacker.com is decent.

 
Shahid June 7, 2011

@Justin

Many thanks.

You see, when you talk about my DNS queries being sniffed on open networks, that’s the kind of thing I’d never have realised. That’s the kind of thing it’d be great to learn. lifehacker doesn’t teach those things in general, but there might be other sites?

On another note, I’ve stopped (not terminated) my EC2 instance, but the Elastic IP I’ve got stays active at 1c an hour. Is there anything else worth keeping it around for? Otherwise the elastic IP on its own costs me $87 a year!

Thanks again.

Reply
 

[…] Protect yourself from FireSheep with Amazon EC2 + OpenVPN for $0.50 a month (stratumsecurity.com) […]

Reply
 
Jason Bourne October 18, 2011

Can someone firm that this still works if I create an account and do this /today/? I need to enter credit card info to create an Amazon AWS account and I don’t want to be accidentally charged. I’m just in Europe for a few months and would love to be able to keep using Spotify and Netflix and Hulu.

Reply
 
Justin October 27, 2011

It still works, but you will be charged a nominal fee each month. The credit card is needed to pay this fee. Your fee will be higher if you stream video through it.

 
RTC S01E04: Breaking Bad October 20, 2011

[…] Micro Instanzen als YouTube Proxy [1] [2] […]

Reply
 
Craig Patik October 22, 2011

I found a way past Step 16 (Cyberduck). I downloaded Transmit (free trial from Panic) and instead of setting up an S3 connection I chose SFTP.
Server name: the IP address of my EC2 instance
User name: ubuntu
Password: click the key icon and browse to the .pem file you made earlier

When you connect you’ll be in the folder called ‘ubuntu’ above an empty file list. This actually /home/ubuntu, so to find your .tar file go up two directories to /, then find /etc/openvpn.

Reply
 

[…] possess personal home SSH server. If you’re peaceful to compensate usually a little, we can get an Amazon EC2 instance with SSH entrance for around $0.50/month or pay $1 one time for entrance to Silence is […]

Reply
 

[…] set up your own personal home SSH server. If you’re willing to pay just a little, you can get an Amazon EC2 instance with SSH access for around $ 0.50/month or pay $ 1 one time for access to Silence is […]

Reply
 

[…] set up your own personal home SSH server. If you’re willing to pay just a little, you can get an Amazon EC2 instance with SSH access for around $US0.50/month or pay $US1 one time for access to Silence is […]

Reply
 

[…] set up your own personal home SSH server. If you’re willing to pay just a little, you can get an Amazon EC2 instance with SSH access for around $0.50/month or pay $1 one time for access to Silence is […]

Reply
 

[…] set up your own personal home SSH server. If you’re willing to pay just a little, you can get an Amazon EC2 instance with SSH access for around $US0.50/month or pay $US1 one time for access to Silence is […]

Reply
 

Leave a Reply