Git Product home page Git Product logo

algo-ng's Introduction

Algo VPN

Join the chat at https://gitter.im/trailofbits/algo Twitter TravisCI Status

Algo VPN is a set of Terraform files that simplify the setup of a personal VPN. It uses the most secure defaults available, works with common cloud providers, and does not require client software on most devices. See our release announcement for more information.

Features

  • Supports only IKEv2 with strong crypto (AES-GCM, SHA2, and P-256) and WireGuard
  • Generates Apple profiles to auto-configure iOS and macOS devices
  • Includes a helper script to add and remove users
  • Blocks ads with a local DNS resolver (optional)
  • Sets up limited SSH users for tunneling traffic (optional)
  • Based on current versions of Ubuntu and StrongSwan
  • Installs to DigitalOcean, Amazon Lightsail, Amazon EC2, Microsoft Azure, Google Compute Engine, Hetzner, Scaleway

Anti-features

  • Does not support legacy cipher suites or protocols like L2TP, IKEv1, or RSA
  • Does not install Tor, OpenVPN, or other risky servers
  • Does not depend on the security of TLS
  • Does not require client software on most platforms
  • Does not claim to provide anonymity or censorship avoidance
  • Does not claim to protect you from the FSB, MSS, DGSE, or FSM

Deploy the Algo Server

The easiest way to get an Algo server running is to let it set up a new virtual machine in the cloud for you.

  1. Setup an account on a cloud hosting provider. Algo supports DigitalOcean (most user friendly), Amazon EC2, Google Compute Engine, and Microsoft Azure.

  2. Download Algo. Unzip it in a convenient location on your local machine.

  3. Install Algo's core dependencies. Open the Terminal.

    • macOS:

      $ brew install terraform
    • Ubuntu (16.04 or later):

      $ sudo apt-get update && sudo apt-get install snapd -y \
      $ sudo snap install terraform
    • Others: Download Terraform binary

  4. List the users to create. Open config.auto.tfvars in your favorite text editor. Specify the users you wish to create in the vpn_users list.

  5. Start the deployment. Return to your terminal. In the Algo directory, run ./algo apply and follow the instructions. There are several optional features available. None are required for a fully functional VPN server.

That's it! You will get the message below when the server deployment process completes. You now have an Algo server on the internet. Take note of the p12 (user certificate) password in case you need it later.

You can now setup clients to connect it, e.g. your iPhone or laptop. Proceed to Configure the VPN Clients below.

Configure the VPN Clients

Certificates and configuration files that users will need are placed in the configs directory. Make sure to secure these files since many contain private keys. All files are saved under a subdirectory named with the IP address of your new Algo VPN server.

Apple Devices

Send users their Apple Profile. Find the corresponding mobileconfig (Apple Profile) for each user and send it to them over AirDrop or other secure means. Apple Configuration Profiles are all-in-one configuration files for iOS and macOS devices. On macOS, double-clicking a profile to install it will fully configure the VPN. On iOS, users are prompted to install the profile as soon as the AirDrop is accepted.

Turn on the VPN. On iOS, connect to the VPN by opening Settings and clicking the toggle next to "VPN" near the top of the list. On macOS, connect to the VPN by opening System Preferences -> Network, finding Algo VPN in the left column and clicking "Connect." On macOS, check "Show VPN status in menu bar" to easily connect and disconnect from the menu bar.

Managing On-Demand VPNs. If you enabled "On Demand", the VPN will connect automatically whenever it is able. On iOS, you can turn off "On Demand" by clicking the (i) next to the entry for Algo VPN and toggling off "Connect On Demand." On macOS, you can turn off "On Demand" by opening the Network Preferences, finding Algo VPN in the left column, and unchecking the box for "Connect on demand."

Android Devices

WireGuard is used to provide VPN services on Android. Install the WireGuard VPN Client. Import the corresponding wireguard/<name>.conf file to your device, then setup a new connection with it. See the Android setup instructions for more detailed walkthrough.

Windows

WireGuard is used to provide VPN services on Windows. Algo generates a WireGuard configuration file, wireguard/<username>.conf, for each user defined in config.cfg.

Install the WireGuard VPN Client. Import the generated wireguard/<username>.conf file to your device, then setup a new connection with it.

Linux Network Manager Clients (e.g., Ubuntu, Debian, or Fedora Desktop)

Network Manager does not support AES-GCM. In order to support Linux Desktop clients, choose the "compatible" cryptography during the deploy process and use at least Network Manager 1.4.1. See Issue #263 for more information.

Linux strongSwan Clients (e.g., OpenWRT, Ubuntu Server, etc.)

Install strongSwan, then copy the included ipsec_user.conf, ipsec_user.secrets, user.crt (user certificate), and user.key (private key) files to your client device. These will require customization based on your exact use case. These files were originally generated with a point-to-point OpenWRT-based VPN in mind.

Ubuntu Server example

  1. sudo apt-get install strongswan libstrongswan-standard-plugins: install strongSwan
  2. /etc/ipsec.d/certs: copy <name>.crt from algo-master/configs/<server_ip>/ipsec/manual/<name>.crt
  3. /etc/ipsec.d/private: copy <name>.key from algo-master/configs/<server_ip>/ipsec/manual/<name>.key
  4. /etc/ipsec.d/cacerts: copy cacert.pem from algo-master/configs/<server_ip>/ipsec/manual/cacert.pem
  5. /etc/ipsec.secrets: add your user.key to the list, e.g. <server_ip> : ECDSA <name>.key
  6. /etc/ipsec.conf: add the connection from ipsec_user.conf and ensure leftcert matches the <name>.crt filename
  7. sudo ipsec restart: pick up config changes
  8. sudo ipsec up <conn-name>: start the ipsec tunnel
  9. sudo ipsec down <conn-name>: shutdown the ipsec tunnel

One common use case is to let your server access your local LAN without going through the VPN. Set up a passthrough connection by adding the following to /etc/ipsec.conf:

conn lan-passthrough
leftsubnet=192.168.1.1/24 # Replace with your LAN subnet
rightsubnet=192.168.1.1/24 # Replace with your LAN subnet
authby=never # No authentication necessary
type=pass # passthrough
auto=route # no need to ipsec up lan-passthrough

To configure the connection to come up at boot time replace auto=add with auto=start.

Other Devices

Depending on the platform, you may need one or multiple of the following files.

  • ipsec/manual/cacert.pem: CA Certificate
  • ipsec/manual/.p12: User Certificate and Private Key (in PKCS#12 format)
  • ipsec/manual/.conf: strongSwan client configuration
  • ipsec/manual/.secrets: strongSwan client configuration
  • ipsec/apple/.mobileconfig: Apple Profile
  • wireguard/.conf: WireGuard configuration profile
  • wireguard/.png: WireGuard configuration QR code

Setup an SSH Tunnel

If you turned on the optional SSH tunneling role, then local user accounts will be created for each user in config.cfg and SSH authorized_key files for them will be in the configs directory (user.ssh.pem). SSH user accounts do not have shell access, cannot authenticate with a password, and only have limited tunneling options (e.g., ssh -N is required). This ensures that SSH users have the least access required to setup a tunnel and can perform no other actions on the Algo server.

Use the example command below to start an SSH tunnel by replacing user and ip with your own. Once the tunnel is setup, you can configure a browser or other application to use 127.0.0.1:1080 as a SOCKS proxy to route traffic through the Algo server.

ssh -D 127.0.0.1:1080 -f -q -C -N user@ip -i configs/<server_ip>/ssh-tunnel/<user>.pem

SSH into Algo Server

Your Algo server is configured for key-only SSH access for administrative purposes. Open the Terminal app, cd into the algo-master directory where you originally downloaded Algo, and then use the command listed on the success message:

ssh -i configs/algo.pem user@ip

where user is either root or ubuntu as listed on the success message, and ip is the IP address of your Algo server. If you find yourself regularly logging into the server then it will be useful to load your Algo ssh key automatically. Add the following snippet to the bottom of ~/.bash_profile to add it to your shell environment permanently.

ssh-add ~/.ssh/algo > /dev/null 2>&1

Adding or Removing Users

If you chose the save the CA certificate during the deploy process, then Algo's own scripts can easily add and remove users from the VPN server.

  1. Update the vpn_users list in your config.auto.tfvars
  2. Open a terminal, cd to the algo directory, and run the command: ./algo update-users

After this process completes, the Algo VPN server will contains only the users listed in the config.auto.tfvars file.

Additional Documentation

If you read all the documentation and have further questions, join the chat on Gitter.

Endorsements

I've been ranting about the sorry state of VPN svcs for so long, probably about time to give a proper talk on the subject. TL;DR: use Algo.

-- Kenn White

Before picking a VPN provider/app, make sure you do some research https://research.csiro.au/ng/wp-content/uploads/sites/106/2016/08/paper-1.pdf ... – or consider Algo

-- The Register

Algo is really easy and secure.

-- the grugq

I played around with Algo VPN, a set of scripts that let you set up a VPN in the cloud in very little time, even if you don’t know much about development. I’ve got to say that I was quite impressed with Trail of Bits’ approach.

-- Romain Dillet for TechCrunch

If you’re uncomfortable shelling out the cash to an anonymous, random VPN provider, this is the best solution.

-- Thorin Klosowski for Lifehacker

Support Algo VPN

Flattr PayPal Patreon Bountysource

All donations support continued development. Thanks!

  • We accept donations via PayPal, Patreon, and Flattr.
  • Use our referral code when you sign up to Digital Ocean for a $10 credit.
  • We also accept and appreciate contributions of new code and bugfixes via Github Pull Requests.

Algo is licensed and distributed under the AGPLv3. If you want to distribute a closed-source modification or service based on Algo, then please consider purchasing an exception . As with the methods above, this will help support continued development.

algo-ng's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

algo-ng's Issues

Setup option mistake

$ ./algo apply

    What provider would you like to use?
      1. DigitalOcean
      2. Amazon EC2
      3. Google Compute Engine

    Enter the number of your desired provider
    : 3


    Name the vpn server:
    [algo-local]: 

    Enter your azure secret id (https://github.com/trailofbits/algo/blob/master/docs/cloud-azure.md)
    You can skip this step if you want to use your defaults credentials from ~/.azure/credentials
    [pasted values will not be displayed]
    [...]: 

the script algo

  case "$ALGO_PROVIDER" in
    1|digitalocean) ALGO_PROVIDER=digitalocean; digitalocean; ;;
    2|ec2) ALGO_PROVIDER=ec2; ec2; ;;
    3|azure) ALGO_PROVIDER=azure; azure; ;;
    3|gce) ALGO_PROVIDER=gce; gce; ;;
    # 5|non_cloud) ALGO_PROVIDER=non_cloud; non_cloud; ;;
    *) exit 1 ;;
  esac

duplicated entry

3-> azure
3-> gce
gce never reach.

Master readme doc link brokens

This md doc not exists

- Deploy from [Windows](docs/deploy-from-windows.md)

After, looking at source code, there is NO .md in the docs folder, except one.

Current problems

  • Certificates provisioning happens on the server. I would prefer to avoid the CA key leaking from the client's machine. Terraform doesn't allow to setup the password for private keys yet. Otherwise we may use any secure storage to keep the CA private with terraform.
  • How to get terraform binary? The better way is to build a gitlab page which detects user's OS and proposes the link to download terraform. This can simplify the installation. But bash wrapper would work as well
  • Documentations. Need to build a few more pages to describe the modules and how advanced users can use them separately in automated builds.
  • More then 1 command to deploy Algo without the wrapper. Not a problem actually, but would be good to simplify this.

Is this project still active?

I'm curious what the status is for this project... Are you still planning to re-write algo in terraform? Or is this idea abandoned now?

blacklist.txt is missing, prevents dnscrypt-proxy from loading

Clean install on DigitalOcean. I have the following settings:

export WORKSPACE="default"
export ALGO_PROVIDER=1
export DIGITALOCEAN_TOKEN=<< MY TOKEN >> 
export ALGO_REGION=sfo2
export ALGO_SERVER_NAME=algo

./algo apply

After connecting to the server, my machine can not resolve DNS. Was debugging the server and found this:

# service dnscrypt-proxy status

● dnscrypt-proxy.service - DNSCrypt-proxy client
   Loaded: loaded (/lib/systemd/system/dnscrypt-proxy.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/dnscrypt-proxy.service.d
           └─99-capabilities.conf
   Active: failed (Result: exit-code) since Tue 2019-12-10 06:16:57 UTC; 2s ago
     Docs: https://github.com/jedisct1/dnscrypt-proxy/wiki
  Process: 1443 ExecStart=/usr/bin/dnscrypt-proxy --config /etc/dnscrypt-proxy/dnscrypt-proxy.toml (code=exited, status=255/E
 Main PID: 1443 (code=exited, status=255/EXCEPTION)

Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: config option `refused_code_in_responses` is deprecated, use `blocked_
Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: dnscrypt-proxy 2.0.33
Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: Network connectivity detected
Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: /etc/dnscrypt-proxy/public-resolvers.md: open sf-y7etj5gtjqfxxjmy.tmp:
Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: Source [public-resolvers] loaded
Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: Firefox workaround initialized
Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: Loading the set of blocking rules from [blacklist.txt]

# ------> issue bellow:
Dec 10 06:16:57 solar-1575956637 dnscrypt-proxy[1443]: open blacklist.txt: no such file or directory
Dec 10 06:16:57 solar-1575956637 systemd[1]: dnscrypt-proxy.service: Main process exited, code=exited, status=255/EXCEPTION
Dec 10 06:16:57 solar-1575956637 systemd[1]: dnscrypt-proxy.service: Failed with result 'exit-code'.

to resolve the issue:

# ssh into algo machine

# cp example file
cp /etc/dnscrypt-proxy/example-blacklist.txt /etc/dnscrypt-proxy/blacklist.txt

# restart dnscrypt
service dnscrypt-proxy restart

a different solution would be set a terraform provisioner to cp example-blacklist.txt to blacklist.txt or setting the blacklist file to be example-blacklist.txt.

Would create a PR but can not validate this on other services (specifically GCE & Azure). Thank you for this project, please let me know if there is other way I could help.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.