![]() |
|
[Socialites] Algo VPN - Set Up a Personal IPSEC VPN in the Cloud - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45) +--- Forum: Whitehat • Blue Team • Defensive Security (https://hackforums.net/forumdisplay.php?fid=448) +---- Forum: OpSec and OSINT (https://hackforums.net/forumdisplay.php?fid=322) +---- Thread: [Socialites] Algo VPN - Set Up a Personal IPSEC VPN in the Cloud (/showthread.php?tid=5602471) |
[Socialites] Algo VPN - Set Up a Personal IPSEC VPN in the Cloud - SUI-3183372 - Apr 17, 2017 Download: https://mega.nz/#!V5wgCI7S!o7K_dIw8H8Zhex8UfEYqQGSeG898nV75ZZI4TJ6Tkkk ![]() Algo VPN Algo VPN is a set of Ansible scripts that simplify the setup of a personal IPSEC 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
Anti-features
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.
You can now setup clients to connect it, e.g. your iPhone or laptop. Proceed to Configure the VPN Clients below. Note: If you want to run Algo again at any point in the future, you must first "reactivate" the dependencies for it. To reactivate them, open your terminal, use cd to navigate to the directory with Algo, then run source env/bin/activate. Advanced users who want to install Algo on top of a server they already own or want to script the deployment of Algo onto a network of servers, please see the Advanced Usage documentation. Configure the VPN Clients Distribute the configuration files to your users, so they can connect to the VPN. 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 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. Android Devices You need to install the strongSwan VPN Client for Android 4 and newer because no version of Android supports IKEv2. Import the corresponding user.p12 certificate to your device. Windows Windows clients have a more complicated setup than most others. Follow the steps below to set one up:
If you want to perform these steps by hand, you will need to import the user certificate to the Personal certificate store, add an IKEv2 connection in the network settings, then activate stronger ciphers on it via the following PowerShell script: Code Set-VpnConnectionIPsecConfiguration -ConnectionName "Algo" -AuthenticationTransformConstants SHA256128 -CipherTransformConstants AES256 -EncryptionMethod AES256 -IntegrityCheckMethod SHA256 -DHGroup Group14 -PfsGroup noneLinux Network Manager Clients (e.g., Ubuntu, Debian, or Fedora Desktop) Network Manager does not support AES-GCM. In order to support Linux Desktop clients, please choose the "compatible" cryptography 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 16.04 example 1. sudo apt-get install strongswan strongswan-plugin-openssl: install strongSwan 2. /etc/ipsec.d/certs: copy user.crt from algo-master/configs/<name>/pki/certs 3. /etc/ipsec.d/private: copy user.key from algo-master/configs/<name>/pki/private 4. /etc/ipsec.d/cacerts: copy cacert.pem from algo-master/configs/<name>/cacert.pem 5. /etc/ipsec.secrets: add your user.key to the list, e.g. xx.xxx.xx.xxx : ECDSA user.key 6. /etc/ipsec.conf: add the connection from ipsec_user.conf and update leftcert to match the user.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. Replace 192.168.1.1/24 with the subnet your LAN uses: Code conn lan-passthroughOther Devices Depending on the platform, you may need one or multiple of the following files.
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 an 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 is done to ensure that SSH users have the least access required to tunnel through the server and can perform no other actions. 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. Code ssh -D 127.0.0.1:1080 -f -q -C -N user@ip -i configs/ip_user.ssh.pemAdding or Removing Users Algo's own scripts can easily add and remove users from the VPN server.
Additional Documentation
Download: https://mega.nz/#!V5wgCI7S!o7K_dIw8H8Zhex8UfEYqQGSeG898nV75ZZI4TJ6Tkkk Source: TrailOfBits * - Mr. Robot - Apr 18, 2017 Hey man thanks for the great contribution. * - mr robots hungry child - Apr 18, 2017 This is extremely interesting and detailed. Well done! * - 'OverSight - Apr 19, 2017 Wonderful. I didn't read it all but would this be essentially logless? * - SUI-3183372 - Apr 19, 2017 Yes. Then anything additional you don't want stored just point to /dev/null * - SUI-3183372 - Oct 17, 2017 I've begun working with the Socialites usergroup to better maintain my privacy, security, and anonymity threads. This will help me push out thread updates sooner and include more content. This thread will be reviewed and new content should be added in the upcoming days. * - Mi2414 - Oct 18, 2017 I know this article is old, but does this still mean if someone has the PSKs then you are screwed? * - SUI-3183372 - Oct 18, 2017 (Oct 18, 2017 03:40 PM)Amidst Wrote: I know this article is old, but does this still mean if someone has the PSKs then you are screwed? Idk much about the NSA's attack capabilities and whether or not anything has changed since the time period this article talks about (2010), however that article does mention IPSec, which is the protocol this VPN is based off of: Quote:But in 2010, the NSA had already developed tools to attack the most commonly used VPN encryption schemes: Secure Shell (SSH), Internet Protocol Security (IPSec), and Secure Socket Layer (SSL) encryption. |