Merge branch 'master' of github.com:trailofbits/vpn

README.md

@@ -15,8 +15,9 @@ Algo (short for "Al Gore", the **V**ice **P**resident of **N**etworks everywhere
 
 ## Anti-features
 
-* Does not support legacy cipher suites or protocols, like L2TP or IKEv1
+* Does not support legacy cipher suites or protocols like L2TP, IKEv1, or RSA
 * Does not install Tor, OpenVPN, or other insecure servers
+* Does not depend on the security of [TLS](https://tools.ietf.org/html/rfc7457)
 * Does not require client software on most platforms
 * Does not claim to provide anonymity
 * Does not claim to protect you from the [FSB](https://en.wikipedia.org/wiki/Federal_Security_Service), [MSS](https://en.wikipedia.org/wiki/Ministry_of_State_Security_(China)), [DGSE](https://en.wikipedia.org/wiki/Directorate-General_for_External_Security), or [FSM](https://en.wikipedia.org/wiki/Flying_Spaghetti_Monster)
@@ -46,8 +47,8 @@ ansible-playbook users.yml -i inventory_users -l example.com
 
 ### Has this been audited?
 
-No. This project is under active development. We're happy to [accept and fix issues](https://github.com/trailofbits/algo/issues) as they are identified.
+No. This project is under active development. We're happy to [accept and fix issues](https://github.com/trailofbits/algo/issues) as they are identified. Use algo at your own risk.
 
 ### Why aren't you using Tor?
 
-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 usesrs. Namely, with algo, users are in control over the gateway routing their traffic. With Tor, users are at the mercy of [actively](https://www.securityweek2016.tu-darmstadt.de/fileadmin/user_upload/Group_securityweek2016/pets2016/10_honions-sanatinia.pdf) [malicious](https://chloe.re/2015/06/20/a-month-with-badonions/) [exit](https://community.fireeye.com/people/archit.mehta/blog/2014/11/18/onionduke-apt-malware-distributed-via-malicious-tor-exit-node) [nodes](https://www.wired.com/2010/06/wikileaks-documents/).
+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](https://www.securityweek2016.tu-darmstadt.de/fileadmin/user_upload/Group_securityweek2016/pets2016/10_honions-sanatinia.pdf) [malicious](https://chloe.re/2015/06/20/a-month-with-badonions/) [exit](https://community.fireeye.com/people/archit.mehta/blog/2014/11/18/onionduke-apt-malware-distributed-via-malicious-tor-exit-node) [nodes](https://www.wired.com/2010/06/wikileaks-documents/).

common.yml

@@ -94,7 +94,7 @@
         - "#                    Your IPsec server is running.                     #"
         - "#  Config files and X.509 certificates in the directory: ./configs/    #"
         - "#          After connect go to https://www.dnsleaktest.com/            #"
-        - "#        and ensure that all your traffic pass through the VPN.        #"
+        - "#        and ensure that all your traffic passes through the VPN.      #"
         - "#----------------------------------------------------------------------#"    
   
   handlers:
@@ -109,5 +109,3 @@
       
     - name: flush routing cache
       shell: echo 1 > /proc/sys/net/ipv4/route/flush     
-
-