How to use Tor as a socks5 proxy

Yes, you can definitely use Tor as a socks5 proxy. Never heard of it? Tor is a network that uses peer-to-peer connections to allow people securely surfing the web without leaving any trace. Originally developed by U.S. Naval Research Laboratory, now Tor is being used by millions of Internet users. When you start a Tor session, it also comes with a socks5 proxy at port 9150 on your computer. So you can easily use any application that supports socks5 proxy under Tor with a simple configuration. Remember that Tor application need to be opened the entire time. Again, the socks5 address for Tor proxy is : socks5://localhost:9150

Increase “a little” privacy by disabling third party cookies

Have you remember searching for something or browsing some products, and the next day Facebook recommends the same or similar type of products? Companies these days try pretty hard to track your every movement. Cookies is one of the main tracking panel. 1+ button, Like button, social button, … in general come with a tracking code that can track your behavior on the current website, and if, by accident (but very likely) you also logged in to Google, Facebook, …, these information will be linked to your Google, Facebook, … accounts. These information will be used to track, identify and ultimately, make money. If you fell comfortable about this, that’s completely fine. However, if you fell disturbing and disguising, here are some little tricks that can gain you a little privacy. Install AdBlock or AdBlockPlus. They are not the same, by the way. Disable third party cookies. On Safari, it’s located at Preferences -> Privacy and select “Allow from current website only”. On Chrome, it’s located at Settings -> Show advanced settings… -> Content settings… and check “Block third-party cookies and site data”. I don’t use any other browser, so I can’t tell where this option located, but it should be pretty easy to figure it out. Do-Not-Track option does not help at all, so don’t bother trying this. Hope this make you fell a little secure.

Update on DigitalOcean’s connectivity issue with 4.2.2.2

This is the followup post of the following report: Seems that DigitalOcean haven’t fixed anything yet. 8 days since my last post. This page https://status.digitalocean.com/ show no information regarding this issue. Other people also reported similar behavior. Come on, do something DigitalOcean! Here is the latest benchmarks from my server to 3 different DNS provider: 4.2.2.2 (Level3), 8.8.8.8 (Google) and 208.67.222.222 (OpenDNS). I issued 10 dig queries for google.com, each of them 10 seconds apart. 6/10 queries sent to 4.2.2.2 are timed out. None of them happen for 8.8.8.8 and 208.67.222.222 tuananh@codepie:~$ for i in {1..10}; do dig google.com @4.2.2.2 | grep ‘connection timed out’; sleep 10; done; ;; connection timed out; no servers could be reached ;; connection timed out; no servers could be reached ;; connection timed out; no servers could be reached ;; connection timed out; no servers could be reached ;; connection timed out; no servers could be reached ;; connection timed out; no servers could be reached tuananh@codepie:~$ for i in {1..10}; do dig google.com @8.8.8.8 | grep ‘connection timed out’; sleep 10; done; tuananh@codepie:~$ for i in {1..10}; do dig google.com @208.67.222.222 | grep ‘connection timed out’; sleep 10; done;