TorrentFreaks Annual VPN Questionnaire (2018)

[LZ1 672]

Hello!

 

This list and perhaps site too, should be taken with a grain of salt, not least because:

 

Note: several of the providers listed in this article are TorrentFreak sponsors. We reserve the first three spots for our sponsors, as a courtesy.

 

But it's still interesting to see the answers.

 

Here's how AirVPN responded:

 

1. Do you keep ANY logs which would allow you to match an IP-address and a time stamp to a user of your service? If so, exactly what information do you hold and for how long?

1. No, we don’t.

 

2. What is the name under which your company is incorporated, and under which jurisdiction does your company operate?

2. The name of the company is Air and it is located in Italy.

 

3. What tools are used to monitor and mitigate abuse of your service, including limits of concurrent connections if these are enforced?

3. We do not use any monitoring or traffic inspection tools. We do associate a connections counter for each account to enforce the limit of five simultaneous connections per account. We also promptly investigate any service (website etc.) running behind our service to prevent phishing and other scams (malware spreading, bot controllers, etc) if we receive a complaint about them. However, checking those services after a complaint or a warning from a third-party does not require any traffic monitoring.

 

4. Do you use any external email providers (e.g. Google Apps), analytics, or support tools ( e.g Live support, Zendesk) that hold information provided by users?

4. Absolutely not.

 

5. In the event you receive a DMCA takedown notice or a non-US equivalent, how are these handled?

5. They are ignored.

 

6. What steps are taken when a court orders your company to identify an active or past user of your service? How would your company respond to a court order that requires you to log activity going forward? Has any of this ever happened?

6. The matter is handled by our law firm which explains to the competent authorities how our system works and why it is not possible to track a user “ex-post” when such identification requires access to traffic logs, which simply do not exist. We have so far not received any order trying to force us to “log activity going forward” and we would not be able to comply for strictly technical reasons.

 

7. Is BitTorrent and other file-sharing traffic allowed on all servers? If not, why?

7. Yes, BitTorrent (just like any other protocol) is allowed on all servers without any re-routing.

 

8. Which payment systems/providers do you use? Do you take any measures to ensure that payment details can’t be linked to account usage or IP-assignments?

8. Nowadays we use Coinpayments, BitPay, PayPal and Avangate. We accept a wide variety of cryptocurrencies and several credit cards. We also planned to accept payments in Bitcoin (and some other cryptocurrency) directly in late 2018, with no need for any third party payment processor, which anyway does not require any personal data to complete a transaction.

We do not keep any information about account usage and/or IP address assignments, so there can’t be any correlation with any payment. As usual a customer needs to consider that any payment via a credit card or PayPal will be recorded for an indefinite amount of time by the respective financial companies. We also accept cryptocurrencies inherently designed to provide a strong layer of anonymity.

 

9. What is the most secure VPN connection and encryption algorithm you would recommend to your users?

9. We recommend only and exclusively OpenVPN. A proper configuration must include TLS mode, Perfect Forward Secrecy, 4096 bit Diffie-Hellmnn keys, and at least 2048 bit (preferably 4096 bit) RSA keys. About the channels ciphers, AES-256 both on the Control Channel and the Data Channel is an excellent choice, while digests like HMAC SHA (when you don’t use an AED cipher such as AES-GCM) for authentication of packets are essential to guarantee integrity (preventing for example injection of forged packets in the stream), both on the Control and the Data channels.

Our service provides all of the above. About Elliptic Curve Cryptography, since it is finally of public domain that at least one random number generator (Dual_EC_DRBG) had a backdoor, and that an NSA program did exist with the aim to implement backdoors in some curves and then have exactly those curves recommended by NIST, momentarily we would suggest to drop ECC completely, just to stay on the safe side and according to Bruce Schneier’s considerations.

 

10. Do you provide tools such as “kill switches” if a connection drops and DNS leak protection?

10. Yes, of course. They are integrated in our free and open source software “Eddie” released under GPLv3. Anyway, usage of our software is not mandatory to access our service, so we also provide guides to prevent any kind of traffic leaks outside the VPN “tunnel” on a variety of systems.

 

11. Do you have physical control over your VPN servers and network or are they outsourced and hosted by a third party (if so, which ones)? Do you use your own DNS servers? (if not, which servers do you use?)

11. The VPN server management is never outsourced. Even the IPMI, which has proven to be the source of extremely dangerous vulnerabilities, is patched and access-restricted by the AirVPN core management persons only. The Air company does not own datacenters. Owning a datacenter would put Air in a vulnerable position in the scenario described in your question number 6 (second part: court order to start logging traffic).

 

12. What countries are your servers physically located? Do you offer virtual locations?

12. We do not offer “virtual” locations. No IP address geo-location trick, hidden re-routing or any other trick is ever performed. We do not use Virtual Servers at all. Currently, we have physical (bare metal) servers really located in the following countries: Austria, Belgium, Bulgaria, Canada, Czech Republic, Germany, Hong Kong, Japan, Latvia, Lithuania, Netherlands, Norway, Romania, Singapore, Spain, Sweden, Switzerland, Ukraine, United Kingdom, United States.

 

 

What do you think?

 

I think it's curious how many answer number 1 with some sort of "No we don't track users" and then when you get to number 4, they say "But we use XYZ Google system".

[go558a83nk 362]

My only concern with that is they didn't seem to answer question 11 thoroughly, especially the DNS question.  I don't really care, but wonder what other people might think of that. 

[zhang888 1066]

My only concern with that is they didn't seem to answer question 11 thoroughly, especially the DNS question.  I don't really care, but wonder what other people might think of that. 

 

DNS servers are obviously a self made custom solution, which sets up the origin of the request to the exit IP of the server for all queries,

which will be true if you use the internal 10.x.0.1 subnet as the DNS server of course, otherwise it will be overridden by your OS.

This is the default of OpenVPN configs and Eddie, so a DNS leak protection is guaranteed, unless you use Windows and OpenVPN < 2.3.9.

 

This is not really a good thing for Torrentfreak to mix 2 completely unrelated questions into 1, so the obvious answer was focusing on real

bare-metal servers vs. virtual ones, which is far more important than the DNS setup of the provider. The DNS setup is almost an irrelevant

side question, since anyone can override this setting (and it is actually recommended to do so, see below) and run something like DNScrypt client on top.

This way even if you don't trust your VPN provider, they will not be able to see your DNS queries under any condition, even if they fully log all outgoing DNS.

[Staff 9972]

@zhang888

 

Well, there is a special case for which you really want that the DNS server address matches the VPN gateway address (as it happens in Air if the client accepts the DNS push), i.e. when you are in an untrusted network. It's the most secure method to prevent DNS hijacking, an exploit which is possible only when the mentioned addresses do not match.

 

We probably should have emphasized this aspect because of this almost-exclusive feature of AirVPN, unfortunately the question was messed up as you noticed.

 

Kind regards