(How to) Signup for SecureMe
If you wish to have a safe and private way to surf the internets while you're at a public wifi hotspot, or somewhere like a hotel "free" network or whatnot, why not consider using a VPN + proxy + DNS resolver combination?
SecureMe is a project I started to try out and get some experience from running an operational combination like this, and I have been using it without much issues for the past quarter year to date.
I'm opening this as a service to people who'd like to make use of this service too, and for no minimum cost! I only ask for the following:
1. feedback/suggestions/complaints/compliments!
2. (if you're feeling generous) donations to help me upkeep my server at least (I don't intend to strike it rich with this anyway) 
If you wish to use this, email me at secureme{@T}rayfoo[dot]info to enquire on availability. Alternatively you could tweet or FB me...
I'll support this as much as possible where time/resources permits, but for now I'd suggest that (at least) the slightly more technically inclined try this.
SecureMe so far…
Have been using my VPN + proxy + dns resolver combination (or the so-called SecureMe project) for a while to date, and it has served my pretty well so far.. I primarily use this at public wifi hotspots like Wireless@SG, where the network is not trusted. Of course this could be extended to apply in networks which aren't necessarily private or trusted, which works very well for people running in paranoia mode (like me).
A short review on the different parts of this system so far...
OpenVPN client fails after running update-resolv-conf
OpenVPN client on Ubuntu "suddenly" stopped working. A look through the logs showed that the update-resolv-conf script seems to be failing...
ovpn-openvpn[3552]: /etc/openvpn/update-resolv-conf tun0 1500 1542 x.x.x.x x.x.x.x init
ovpn-openvpn[3552]: script failed: external program exited with error status: 1
A quick trace of the update-resolv-conf script shows that the problem's with resolvconf:
resolvconf: Error: /etc/resolv.conf must be a symlink
And the fix for that based on another solution:
sudo rm /etc/resolv.conf
sudo ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf