Home Blog

Posts Tagged ‘vpn’

New Maidenhead, UK server added

Tuesday, July 29th, 2014

This is just a quick note that a new Maidenhead, United Kingdom located server, UK14, has just been added to our network. You can connect to it either via our Identity Cloaker application(s), OpenVPN, L2TP over IPSec or PPTP VPN.

If you experience any issues with the new server, please contact our customer support.

 

New Madrid, Spain located server available

Friday, July 4th, 2014

A new server located in┬áMadrid, Spain has been recently added to our network. The ES1 server is now accessible both via our Identity Cloaker application, as well as via OpenVPN and “L2TP over IPSec” VPN on multiple devices. The setup is the same as for our other servers.

If you experience any performance or reliability issues with the new server, please do not hesitate and contact our customer support.

 

The Heartbleed Bug – SSL vulnerability

Wednesday, April 9th, 2014

Some customers contacted us Yesterday regarding the recently found “Heartbleed Bug” which compromises SSL encryption. For details on this dangerous bug, please read:

http://heartbleed.com

All of our servers are now using OpenSSL versions that are *not* affected by the Heartbleed bug. 90% of our servers are running CentOS 5.x with OpenSSL 0.9.8 which has never been affected and only a few servers are running CentOS 6.x. Updated version of the OpenSSL library with workaround patch was already applied Yesterday.

Also, please note that only OpenVPN uses SSL, our standard encrypted proxy servers as well as “L2TP over IPSec” VPN (uses mostly by our iPhone/iPad/OS X and some Android customers) have never been affected by this bug.

An interesting fact to mention is that if you were using Identity Cloaker in the encrypted mode, or connected via VPN and visited an SSL enabled website, the connection was, of course, encrypted by SSH (if using our encrypted proxy servers) or via VPN, which means the potential attacker was not able to take advantage of the Heartbleed bug.

Basically, you were adding another layer of encryption to the (possibly vulnerable) SSL encryption.

 

Contact | Helpdesk | Privacy Policy | Terms Of Service
Join the Blue Ribbon Online Free Speech Campaign