Algo VPN (short for "Al Gore", the Vice President of Networks everywhere for inventing the Internet) is a set of Ansible scripts that simplifies the setup of a personal IPSEC VPN. It contains the most secure defaults available, works with common cloud providers, and does not require client software on most devices.
- Supports only IKEv2 w/ a single cipher suite: AES-GCM, HMAC-SHA2, and P-256 DH
- Generates Apple Profiles to auto-configure iOS and macOS devices
- Provides helper scripts to add and remove users
- Blocks ads with a local DNS resolver and HTTP proxy (optional)
- Sets up limited SSH users for tunneling traffic (optional)
- Based on current versions of Ubuntu and strongSwan
- Installs to DigitalOcean, Amazon EC2, Google Cloud Engine, Microsoft Azure or your own server
- 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
The easiest way to get an Algo server running is to let it setup a new virtual machine in the cloud for you.
- Install the dependencies for your operating system:
OS X: sudo easy_install pip && sudo pip install -r requirements.txt
Linux (deb-based): sudo easy_install pip && sudo apt-get install libssl-dev && sudo pip install -r requirements.txt
- Open the file
config.cfgin your favorite text editor. Specify the users you wish to create in theuserslist. - Start the deploy and follow the instructions:
./algo
That's it! You now have an Algo VPN server on the internet.
Note: for local or scripted deployment instructions see the Advanced Usage documentation.
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 prefixed with the IP address of the Algo VPN server.
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 and installing a profile will fully configure the VPN.
You need to install the StrongSwan VPN Client for Android 4 and newer. Import the corresponding user.p12 certificate to your device. It's very simple to configure the StrongSwan VPN Client, just make a new profile with the IP address of your VPN server and choose which certificate to use.
Import your user certificate to your Personal certificate store and your CA certificate to the Local Machine Trusted Root certificate store. Then, add an IKEv2 connection in the network settings and activate additional ciphers for it via Powershell (change the ConnectionName to the name of your IKEv2 connection):
Set-VpnConnectionIPsecConfiguration -ConnectionName "Algo" -AuthenticationTransformConstants SHA25612 8 -CipherTransformConstants AES256 -EncryptionMethod AES256 -IntegrityCheckMethod SHA256 -DHGroup Group14 -PfsGroup none
Note that an all-in-one Powershell script that imports your personal certificate, sets up the VPN connection, and activates the stronger ciphers for it is included in the configs folder.
Find the included user_ipsec.conf, user_ipsec.secrets, user.crt (user certificate), and user.key (private key) files and copy them to your client device. These may be useful if you plan to set up a point-to-point VPN with OpenWRT or other custom device.
Depending on the platform, you may need one or multiple of the following files.
- ca.crt: CA Certificate
- user_ipsec.conf: StrongSwan client configuration
- user_ipsec.secrets: StrongSwan client configuration
- user.crt: User Certificate
- user.key: User Private Key
- user.mobileconfig: Apple Profile
- user.p12: User Certificate and Private Key (in PKCS#12 format)
- user_windows.ps1: Powershell script to setup a VPN connection on Windows
If you turned on the optional SSH tunneling role, then local user accounts will be created for each user in config.cfg and an SSH authorized_key files for them will be in the configs directory (user.ssh.pem). SSH user accounts do not have shell access and their tunneling options are limited (ssh -N is required). This is done to ensure that users have the least access required to tunnel through the server.
Use the command below to start an SSH tunnel, replacing ip and user 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 Algo.
ssh -D 127.0.0.1:1080 -f -q -C -N user@ip -i configs/ip_user.ssh.pem
Algo's own scripts can easily add and remove users from the VPN server.
- Update the
userslist in yourconfig.cfg - Run the command:
./algo update-users
The Algo VPN server now contains only the users listed in the config.cfg file.
No. This project is under active development. We're happy to accept and fix issues as they are identified. Use Algo at your own risk.
The goal of this project is not to provide anonymity, but to ensure confidentiality of network traffic while traveling. Tor introduces new risks that are unsuitable for Algo's intended users. Namely, with Algo, users are in control over the gateway routing their traffic. With Tor, users are at the mercy of actively malicious exit nodes.
Racoon does not support IKEv2. Racoon2 supports IKEv2 but is not actively maintained. When we looked, the documentation for StrongSwan was better than the corresponding documentation for LibreSwan or OpenSwan. StrongSwan also has the benefit of a from-scratch rewrite to support IKEv2. I consider such rewrites a positive step when supporting a major new protocol version.
I would, but I don't know of any suitable ones. If you're in the position to fund the development of such a project, contact us. We would be interested in leading such an effort. At the very least, I plan to make modifications to StrongSwan and the environment it's deployed in that prevent or significantly complicate exploitation of any latent issues.
OpenVPN does not have out-of-the-box client support on any major desktop or mobile operating system. This introduces user experience issues and requires the user to update and maintain the software themselves. OpenVPN depends on the security of TLS, both the protocol and its implementations, and we simply trust the server less due to past security incidents.
Alpine Linux is not supported out-of-the-box by any major cloud provider. We are interested in supporting Free-, Open-, and HardenedBSD. Follow along or contribute to our BSD support in this issue.