After countless hours of development and testing by our desktop client development team and QA guys, we are ready to release the latest update to the LiquidVPN clients for Windows and Mac. Both Mac and Windows clients have pretty much the same features so I will use the Mac release (ver. 1.12) here and point out any differences for Windows. There is a long list of new features included with LiquidVPN version 1.12 (Mac) and quite a bit of re-worked logic behind the scenes. Many of the new features have been recommendations from our users. Let’s take a look at what LiquidVPN version 1.12 has to offer.
360° Network Protection with Liquid Lock
If you are the type of person that worries about their VPN leaking personal data or giving away your real location due to an exploit or some zero-day malware like WebRTC did last year then Liquid Lock is going to be a game changer for you. Liquid Lock is more than just a VPN kill switch. Liquid Lock uses PF rules which are built into every version of OS X past Lion. What we have done is completely cut your device off from the Internet, and then we open a tiny little hole that can only reach our VPN servers and required infrastructure servers to create an encrypted tunnel between the two locations. Any attempt to circumvent the encrypted tunnel is dropped unless you have given it explicit permission to bypass the firewall. An example of this is your local network traffic. Because this uses PF, it is supported universally and will not fail where other solutions will. The Windows version of Liquid Lock uses the Windows Filtering Platform API to achieve the same thing. It is the reason that the Windows client took several more beta versions to finish quality assurance testing.
A Sneak Peak of the Liquid Lock Interface
You can enable Liquid Lock by clicking the big blue button and agreeing to the warning that is displayed afterwards. If you go to the settings, you will see the Liquid Lock tab. From here you can easily allow local LAN traffic to bypass Liquid Lock and set external addresses that are allowed to bypass Liquid Locks protection.
Informative and Simple Streamlined Interface
Two very popular user interface requests that made it into this build are the addition of the server name display on the connect button and in the server selection screen. The second significant change is the new streamlined server select screen. We received feedback on the server selection process from lots of users. Our main goal is a client that works with the broad spectrum of LiquidVPN users. Inexperienced users can be intimidated by ports, topologies and protocols and would rather it just work. Power users, on the other hand, want quick access to these very same features. The compromise we came up with should urge our inexperienced users to play around some and satisfy our power users need for easy access to the features. Now users can choose their Protocol and Topology without opening the settings.
Behind the Scene Changes
The final LiquidVPN client changes are all coding logic changes. There is a much-improved method of detecting Internet connectivity and we have added alternative methods of getting the VPN server list in case the LiquidVPN domain name is blocked. There have been several improvements made to the way LiquidVPN processes and handles OpenVPN configuration files and finally we have done some OS based network and adapter optimizations that will improve performance across the network.
Control your DNS from the LiquidVPN Interface
LiquidDNS is our private smart DNS network that keeps your DNS queries encrypted and can be used to stream your favorite USA and UK content from every one of our servers. DNS is how your device finds things on the internet. In the past, advanced users needing custom DNS settings were forced to make the changes manually. It is time-consuming and sometimes DNS caching turns what should be a simple task into a somewhat problematic ordeal. We have remedied this by allowing users control over their DNS settings. Selecting Automatic will use our DNS servers. Selecting Manual will use whatever servers you have entered in the DNS Control box.