In this video I show you how to enable Tor on Android with Orbot and prove that the Google Chrome browser is using a real Tor IP address instead of my public IP.
Why an Open Guide?
A lot of information on AWS is already written. Most people learn AWS by reading a blog or a “getting started guide” and referring to the standard AWS references. Nonetheless, trustworthy and practical information and recommendations aren’t easy to come by. AWS’s own documentation is a great but sprawling resource few have time to read fully, and it doesn’t include anything but official facts, so omits experiences of engineers. The information in blogs or Stack Overflow is also not consistently up to date.
This guide is by and for engineers who use AWS. It aims to be a useful, living reference that consolidates links, tips, gotchas, and best practices. It arose from discussion and editing over beers by several engineers who have used AWS extensively.
With Edward Snowden’s shocking revelations that the NSA has for years been working to crack and subvert VPN encryption technologies, together with the fact that it is becoming increasingly obvious that most such technologies have been developed and certified by the US government’s National Institute of Standards and Technology (NIST), may therefore be considered suspect.
With AV, security, and home automation systems all running over IP networks, professional installers have a tremendous opportunity to grow their businesses by offering networking solutions. While installing an IP network can be a daunting task for the uninitiated, by understanding the purpose and function of a few key components—as well as what to look for when selecting those components—a professional installer can easily learn to deliver reliable and powerful IP networking solutions. With this in mind, as a professional installer, the primary components with which you should become familiar are as follows:
If you are deploying SSTP VPN for Windows clients and get the error: "The revocation function was unable to check revocation because the revocation server was offline.", you are most likely using your own internal PKI and the certificate used for SSTP does not have a Certificate Revocation List (CRL) accessible from the outside, so the client machine is failing checking whether or not the certificate has been revoked from the CA. If you simply want to bypass this, you can edit the registry on the client: