Staff

Updated. Please see https://gitlab.com/AirVPN/EddieAndroid/ and feel free to contact us if you have problems to build it. Kind regards

@air521745 We're sorry, the plan to make it available on F-Droid has been dropped. Kind regards

@💩💩💩 Thank you for your feedback! We will consider seriously your suggestions. About point 2, however, that would not be a master password, but something mainly useless. Maybe an option that could meet your needs is simply disabling the Master Password, but that affects security just like your proposal. Letting the user to opt-out from the MP seems the only reasonable way (i.e. the user deliberately and freely renounces to a security feature). About point 7: yes, the app is authorized by Android system. Remember that the Android system option you mention is not strictly meant to prevent any POSSIBLE leak outside a VPN tunnel, but to mitigate them by restricting comms to registered apps only. Also, your ISP sees the IP addresses your system contacts to connect to a VPN, over TLS or not, with Eddie or not. By the way, we don't think that Eddie pings at any time ipleak.net (we will check with ProMind) and when the network is in lock state (by Eddie) the app can't access anything, including ipleak.net. Remember in any case that ipleak.net is controlled by airvpn.org. Connection to it is very important to let the app understand what the best server to connect to can potentially be, as we can't use "ping" in any way to determine round trip times. That's a great feedback, thank you! Kind regards

Hello! On April 2018 we made an important step forward: we began to accept Bitcoin directly, through no intermediaries at all. Today, we're very glad to announce that we are able to accept directly more cryptocurrencies. In alphabetical order: Bitcoin Bitcoin Cash Dash Dogecoin Ethereum Ethereum Classic Litecoin Any intermediary acting as a payment processor is no more required. As we wrote in 2018, we stll feel it as an additional, important step forward in privacy protection. Moreover, cutting out any intermediary is very coherent with cryptocurrencies spirit and unleashes their potential. Kind regards and datalove AirVPN Staff

Hello! We're glad to inform you that we have released Eddie Android edition 2.3. Eddie Android Edition 2.3 is available on the Google Play Store as well as Amazon Appstore. https://play.google.com/store/apps/details?id=org.airvpn.eddie https://www.amazon.com/Eddie-AirVPN-official-OpenVPN-GUI/dp/B07KTD6DH9  You can also download Eddie Android 2.3 apk directly from our repository: https://eddie.website/repository/eddie/android/2.3/org.airvpn.eddie.apk Available languages: Chinese (simplified), Chinese (traditional), Danish, Dutch, English, French, German, Italian, Portuguese, Spanish, Russian, Turkish. Source is code available on GitLab: https://gitlab.com/AirVPN/EddieAndroid/ Eddie for Android is free and open source software released under GPLv3. We invite you to check from independent 3rd parties the lack of trackers code signatures, for example here: https://reports.exodus-privacy.eu.org/en/reports/search/org.airvpn.eddie New in version 2.3: Disabled data backup on uninstall Server statistics shown in Favorite/Forbidden/Countries & Servers groups Logout drops user credentials Native library updated to the latest openvpn3, lz4, mbedtls and asio commits Minor bug fixes See changelog at the end of this post for a complete list  Main features: Free and open source OpenVPN GUI based on OpenVPN 3 The only Android application officially developed by AirVPN Robust, best effort prevention of traffic leaks outside the VPN tunnel Battery-conscious application Low RAM footprint Ergonomic and friendly interface Ability to start and connect the application at device boot Option to define which apps must have traffic inside or outside the VPN tunnel through white and black list Localization in simplified and traditional Chinese, Danish, English, French, German, Italian, Portuguese, Russian, Spanish, Turkish Full integration with AirVPN Enhanced security thanks to locally stored encrypted data through master password Quick one-tap connection and smart, fully automated server selection Smart server selection with custom settings Manual server selection Smart attempts to bypass OpenVPN blocks featuring protocol and server fail-over Full Android TV compatibility including D-Pad support. Mouse emulation is not required. Enhancements aimed to increase accessibility and comfort to visually impaired persons AirVPN servers sorting options Customizable "Favorite" and "Forbidden" servers and countries OpenVPN mimetype support to import profiles from external applications Multiple OpenVPN profile support. The app now imports and manages multiple OpenVPN profiles Support for custom bootstrap servers Support for favorite and forbidden countries AirVPN broadcast messages support User's subscription expiration date is shown in login/connection information The app is aware of concurrent VPN use. In case another app is granted VPN access, Eddie acts accordingly and releases VPN resources Optional local networks access. In such case, local network devices are exempted from the VPN and can be accessed within the local devices Localization override. User can choose the default language and localization from one of the available ones Favorite and forbidden lists can be emptied with a single tap VPN Lock can now be disabled or enabled from settings VPN reconnection in case of unexpected OpenVPN disconnection. (It requires VPN Lock to be disabled) User can generate an OpenVPN profile for any AirVPN server or country and save it in OpenVPN profile manager Server scoring algorithm implementing the latest AirVPN balancing factors in order to determine the best server for quick connection Network name and extra information are shown along with network type Device network status management Kind regards & datalove AirVPN Staff Complete changelog available here: https://gitlab.com/AirVPN/EddieAndroid/blob/master/ChangeLog.txt Changelog 2.3 (VC 23) - Release date: 02 July 2019 by ProMIND [ProMIND] - Updated default manifest - Updated native library - AES-256-GCM is now the default cipher - Language override reported to the log - Improved connection error handling - Added statistics in server tab - Minor bug fixes Changelog 2.3 beta 2 (VC 22) - Release date: 27 June 2019 by ProMIND - [ProMIND] About page and webview function now point to https://airvpn.org - [ProMIND] Updated native library with the latest sub-project branches and releases AirVPNUser.java - [ProMIND] getOpenVPNProfile(): AES-256-GCM is now the default cipher MainActivity.java - [ProMIND] Language override is reported to the application log OpenVPNTunnel.java - [ProMIND] improved connection error handling - [ProMIND] removed doRun() method. Method's body moved to run() VPN.java - [ProMIND] Added CONNECTION_ERROR to Status enum VPNService.java - [ProMIND] Added method handleConnectionError() Changelog 2.3 beta 1 (VC 21) - Release date: 17 May 2019 by ProMIND AndroidManifest.xml - [ProMIND] set android:allowBackup and android:fullBackupOnly to false airvpn_server_listview_group_item.xml - [ProMIND] added server statistics layout ConnectAirVPNServerFragment.java - [ProMIND] AirVPNServerExpandableListAdapter.GroupListViewHolder: added server statistics items - [ProMIND] AirVPNServerExpandableListAdapter.getGroupView(): added server statistics items to HEADER and GROUP types - [ProMIND] createGroupList(): compute server statistics for HEADER and GROUP types AirVPNUser.java - [ProMIND] getUserLocation(): set connection timeout to SupportTools.HTTP_CONNECTION_TIMEOUT - [ProMIND] getUserLocation(): set read timeout to SupportTools.HTTP_READ_TIMEOUT - [ProMIND] logout(): user name, password and current profile are set to empty and forgetAirVPNCredentials() is called native library - [ProMIND] updated to the latest openvpn3, lz4, mbedtls and asio commits manifest.xml - [ProMIND] updated to the latest document

Thank you! Of course. The idea has been floating around since several years ago https://community.openvpn.net/openvpn/wiki/RoadMap The OpenVPN 3 Core Library is based on a different approach, implementing the OpenVPN protocol as a C++ library. This gives lots of the same possibilities and modularity as this draft tried to resolve. Further, OpenVPN 3 is multi-thread capable and integrates with ASIO for all asynchronous processing and socket handling.

We agree, when AES-NI are supported. Note that some processors do support AES-NI but the system doesn't use them (examples: AES-NI disabled at BIOS level; OpenSSL or other SSL library not properly compiled). Also see https://tools.ietf.org/html/rfc8439#appendix-B (however note that the comparison is made between AES-128-GCM and ChaCha20 but a more correct comparison would be with AES-256-GCM because of the 256 bit key size of ChaCha20). Not only the appendix but also important considerations in the introduction and later. Kind regards

Hello! We're very glad to inform you that AirVPN has begun to actively contribute to OpenVPN 3 development. Our first goal has been adding support for ChaCha20 cipher with Poly1305 as authenticator on OpenVPN 3 Data Channel. ChaCha20 is a stream cipher developed by Daniel J. Bernstein which combines strength and remarkable performance. https://en.wikipedia.org/wiki/Salsa20#ChaCha20_adoption When compared with AES-GCM, ChaCha20 offers significant computational relief to all AES-NI non supporting processors, such as ARM processors. ARM processors, routinely used on very many tablets, smart phones, media centers, smart TVs and routers, will get great benefits from OpenVPN with ChaCha20. Our tests show that CPU load caused by ChaCha20 on recent ARM 64 bit processors is at least 50% less than AES-256-GCM, on equal terms, which translates into dramatic performance boost and longer battery life (if you have ever tested Wireguard on an ARM based device you know what we mean). OpenVPN 3 is a client library. However, OpenVPN 2.5, which is currently in beta testing and includes all the necessary servers features, supports ChaCha20 on the Data Channel. Therefore, making OpenVPN 3 with ChaCha20 available to our users and allowing a real life test will be a matter of days. We will progressively release beta clients for Android, Linux, OpenBSD and FreeBSD, in this order. We are considering a porting to OpenIndiana as well. Internal alpha testing has concluded successfully. We have already pulled a merge request to OpenVPN 3 main branch, to let the whole community take advantages from our code, and let OpenVPN developers merge the new code into the main branch if they wish so. https://github.com/OpenVPN/openvpn3/pull/78 Implementation has been designed, developed and programmed for AirVPN by ProMIND, who is also Eddie Android edition developer. Stay tuned, more will come! UPDATE: https://airvpn.org/forums/topic/44069-openvpn-3-development-by-airvpn/ The above linked topic is now the central thread to discuss anything related to OpenVPN 3 development and testing. Kind regards and datalove AirVPN Staff

Hello, we wish (in our setup, we mean) that stunnel accepts any connection to bypass restrictions, even when it will have certificate replacement and therefore it is subjected to MITM exploits. The integrity and data security layer is ensured by the underlying OpenVPN tunnel. stunnel is not there to add anything to security when you use OpenVPN over SSL, it is there to try to punch a hole in the filters through which OpenVPN can establish its tunnel. Kind regards

@idealist You don't understand. With static IP addresses stored on the servers you map uniquely and permanently an IP address to a user. Once that IP address is discovered (no need to crack the server, as we wrote) the correlation is done because we know which user always has that IP address, even if we don't log traffic, and we would give away the information under a court order. Which is exactly what go558a83nk already explained to you. This is not possible with OpenVPN, as the dynamic IP addresses are never correlated to a user once the session is over, they are lost. So if the attacker asks "who has that IP address?" with OpenVPN in our setup we don't know, while with Wireguard in the current (at the time of writing) stage of development we would know. If now or in the future Wireguard will allow dynamic addresses assignments, so that no address must be stored permanently for any client, the problem is resolved, but at the time we wrote the article it was not. Kind regards

The issue has been already explained: the keys and the internal IP addresses are all on the server, and they are on every and each server. They can be used to correlate specific targets and disclose their identities, while on our current setup that's not possible. It makes a world of difference when you consider threat models in which VPN users are specifically targeted. Maybe you don't understand the importance of this menace because you wrote: which is correct in our setup, but incorrect in Wireguard setup. The attacker CAN get the internal IP address via WebRTC for example and: 1) in our setup he/she does not correlate the internal IP address with the client key 2) in Wireguard setup he/she does Once that's done the attacker may obtain legally (via a court order) the payment data of the user because it can ask us which user is linked to a single IP address (and also the user key for subsequent forensic evidence). Since the VPN IP address is static and unique, we would be of course forced to comply. We wish to underline for the last time that the problem has been acknowledged by developers and we had been told that it would be resolved. Kind regards

True, so what? It is not the point we made: having all the keys of all users on each VPN is the core privacy and security issue, while having to map statically the addresses of tens or hunreds of thousand clients is the core operational issue in this case. Having no TCP is a different problem for different reasons (because of systematic Net Neutrality violations). According to stats voluntarily provided by users, at least 50% of VPN users complain about UDP shaping and/or blocking by their ISPs in "Western" countries, and the percentage seems higher in other countries. OpenVPN not only supports TCP for the Data Channel, but also allows tls-crypt, which is important when the VPN software fingerprint detection is used to break the connection, which is routinely enforced by many ISPs especially in mobility. By the way, as we repeatedly stated, the first problem we have addressed is being worked on according to what devs told us, while it's not ruled out that Wireguard will support TCP in the future (an external software is also available right now, but of course we prefer native TCP support) . Last but not least, we are confident that obfuscation too is being studied since when we tested the software (another mandatory feature for our customers for the aforementioned reasons), as well as connections to SOCKS or HTTP proxies (yet another essential feature for all of our customers who work behind some proxy) so let's see what comes out when a stable version is released. Kind regards

You can see the obvious difference. In our setup the attacker needs to wait for a connection to that server from a customer to try to wiretap the private key, while with Wireguard the attacker gets at once all the keys of all the users even when the server is offline. Furthermore we would need to map on every and each server statically tens of thousand IP addresses and keys, which is unacceptable. The fact that the IP addresses are local to the VPN is irrelevant and obvious and does not change anything about the privacy problems we mentioned. There could be a workaround to the problem, but we have been told that the problem will be resolved before Wireguard gets out of the beta phase, so it's useless to study the implementation of a workaround during the beta testing as the authors will implement a solution. That's not what we needed / asked for. If now Wireguard supports TLS pre-auth (important for us for trivial reasons) and certificate verification on a TCP control channel that's excellent but it was not available when we wrote the article. Kind regards

Hello! No it doesn't. Our VPN servers do not store clients keys (and have never kept them). At the time the article was written, with Wireguard you needed to pre-map the VPN IP addresses for clients on each server. That's unacceptable. Of course a VPN is not meant to provide you with an anonymity layer so we add a series of essential features which could not be replicated with Wireguard when the post you refer to was written. We have been told that the mentioned problem will be resolved before a stable version is released. Same thing with client/server authentication, if both pre-auth (what OpenVPN calls "TLS Auth" or "TLS Crypt") and client/server certificate verification in TCP have been implemented in the meantime, we welcome them, but they were anyway NOT available at the time the article you refer to was written. Kind regards

Hello! We're very glad to inform you that a new 1 Gbit/s server located in São Paulo, BR, is available: Lalande. The AirVPN client will show automatically the new server. If you use the OpenVPN client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP. Just like every other "second generation" Air server, Lalande supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.2 and tls-crypt. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. You can check the server status as usual in our real time servers monitor: https://airvpn.org/servers/lalande Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

Hello, we might implement a filtering at VPN DNS level. It's not a trivial decision because it is an attack to Net Neutrality and a violation of our network agnosticism. Once you start selecting content, you are no more necessarily protected by liability exemptions on the behavior of your users. You also set a precedent and you can potentially be forced (legally) to implement wider filtering systems. Our purpose has always been providing our users with a network that's as neutral as possible. Kind regards

Hello! We do not enforce any "cap". You can also see from the tables in the status page that 125 Mbit/s is a performance which is easily beaten. The fact that you experience a constant and exact cap with every and each VPN server, and therefore with different tier1 and tier2 transit providers, hints obviously to a cap inside your network (your very local one network, or your ISP's). https://airvpn.org/status Kind regards

Hello! We're glad to inform you that we are finalizing the beta testing phase of our free and open source software Eddie for Android version 2.3. You can participate to testing by joining the beta community in the Google Play Store here: https://play.google.com/apps/testing/org.airvpn.eddie You can also download the Eddie Android 2.3 beta 2 apk directly from our repository: https://eddie.website/repository/eddie/android/2.3beta2/org.airvpn.eddie.apk The application is fully localized and we look for translators, especially for translations into Japanese, Korean and other languages. If you wish to translate (from English) please contact info@airvpn.org for every detail. Available languages: Chinese (simplified), Chinese (traditional), Danish, Dutch, English, French, German, Italian, Portuguese, Spanish, Russian, Turkish. Eddie for Android is free and open source software released under GPLv3. We invite you to check from independent 3rd parties the lack of trackers code signatures, for example here: https://reports.exodus-privacy.eu.org/en/reports/search/org.airvpn.eddie New in version 2.3: Disabled data backup on uninstall Server statistics shown in Favorite/Forbidden/Countries & Servers groups Logout drops user credentials Native library updated to the latest openvpn3, lz4, mbedtls and asio commits Minor bug fixes See changelog at the end of this post for a complete list Main features: Free and open source OpenVPN GUI based on OpenVPN 3 The only Android application officially developed by AirVPN Robust, best effort prevention of traffic leaks outside the VPN tunnel Battery-conscious application Low RAM footprint Ergonomic and friendly interface Ability to start and connect the application at device boot Option to define which apps must have traffic inside or outside the VPN tunnel through white and black list Localization in simplified and traditional Chinese, Danish, English, French, German, Italian, Portuguese, Russian, Spanish, Turkish Full integration with AirVPN Enhanced security thanks to locally stored encrypted data through master password Quick one-tap connection and smart, fully automated server selection Smart server selection with custom settings Manual server selection Smart attempts to bypass OpenVPN blocks featuring protocol and server fail-over Full Android TV compatibility including D-Pad support. Mouse emulation is not required. Enhancements aimed to increase accessibility and comfort to visually impaired persons AirVPN servers sorting options Customizable "Favorite" and "Forbidden" servers and countries OpenVPN mimetype support to import profiles from external applications Multiple OpenVPN profile support. The app now imports and manages multiple OpenVPN profiles Support for custom bootstrap servers Support for favorite and forbidden countries AirVPN broadcast messages support User's subscription expiration date is shown in login/connection information The app is aware of concurrent VPN use. In case another app is granted VPN access, Eddie acts accordingly and releases VPN resources Optional local networks access. In such case, local network devices are exempted from the VPN and can be accessed within the local devices Localization override. User can choose the default language and localization from one of the available ones Favorite and forbidden lists can be emptied with a single tap VPN Lock can now be disabled or enabled from settings VPN reconnection in case of unexpected OpenVPN disconnection. (It requires VPN Lock to be disabled) User can generate an OpenVPN profile for any AirVPN server or country and save it in OpenVPN profile manager Server scoring algorithm implementing the latest AirVPN balancing factors in order to determine the best server for quick connection Network name and extra information are shown along with network type Device network status management Kind regards & datalove AirVPN Staff Changelog 2.3 beta 2 (VC 22) - Release date: 27 June 2019 by ProMIND - [ProMIND] About page and webview function now point to https://airvpn.org - [ProMIND] Updated native library with the latest sub-project branches and releases AirVPNUser.java - [ProMIND] getOpenVPNProfile(): AES-256-GCM is now the default cipher MainActivity.java - [ProMIND] Language override is reported to the application log OpenVPNTunnel.java - [ProMIND] improved connection error handling - [ProMIND] removed doRun() method. Method's body moved to run() VPN.java - [ProMIND] Added CONNECTION_ERROR to Status enum VPNService.java - [ProMIND] Added method handleConnectionError() Changelog 2.3 beta 1 (VC 21) - Release date: 17 May 2019 by ProMIND AndroidManifest.xml - [ProMIND] set android:allowBackup and android:fullBackupOnly to false airvpn_server_listview_group_item.xml - [ProMIND] added server statistics layout ConnectAirVPNServerFragment.java - [ProMIND] AirVPNServerExpandableListAdapter.GroupListViewHolder: added server statistics items - [ProMIND] AirVPNServerExpandableListAdapter.getGroupView(): added server statistics items to HEADER and GROUP types - [ProMIND] createGroupList(): compute server statistics for HEADER and GROUP types AirVPNUser.java - [ProMIND] getUserLocation(): set connection timeout to SupportTools.HTTP_CONNECTION_TIMEOUT - [ProMIND] getUserLocation(): set read timeout to SupportTools.HTTP_READ_TIMEOUT - [ProMIND] logout(): user name, password and current profile are set to empty and forgetAirVPNCredentials() is called native library - [ProMIND] updated to the latest openvpn3, lz4, mbedtls and asio commits manifest.xml - [ProMIND] updated to the latest document

Hello! To all: is anybody else experiencing blocks from AT&T and/or Wave Broadband? @DieWurst Please feel free to open a ticket at your earliest convenience, if you haven't already done so. Kind regards

Hello! You can't. TLS 1.3 will be supported starting from OpenVPN 2.4.7 in the near future. Quite irrelevant for OpenVPN currently, but stay tuned. TLS 1.3 is available on all of our web servers, where it is not irrelevant at all. Kind regards

Hello! The Servers view settings are specific to the servers, while the Settings view include options for the quick connect (full auto) mode. Also note that in the Settings view you have the option to bypass the protocols chosen by the full auto mode. Kind regards

Hello! Please make sure to check the ticket you opened just in case you did not receive the courtesy e-mail, or simply you did not enter an existing and valid e-mail address. Trial requests are satisfied, according to availability, in 1 - 48 hours usually. Kind regards

Hello! What allegations are correct? For "correct" do you mean at least pressed as charges by a prosecutor? Otherwise your claims are unsubstantiated and play as a part of the smear campaign itself. Because, and it is worth to repeat it, none of the allegations that tried to frame Jacob Appelbaum, (WikiLeaks, Tor Project advocate), Trevor Fitzgibbons (Edward Snowden PR, publisher, WikiLeaks PR), Julian Assange (WikiLeaks), Nadim Kobeissi (Cryptocat) and Peter Todd (Bitcoin Core former developer) as serial rapists arrived at any court, and no prosecutor pressed charges against any of them so far. It is also worth noting that the campaigns to make Appelbaum, Kobeissi and Todd appear as rapists started from claims of the same person (Isis Agora Lovecruft), and that Peter Todd has sued Isis for defamation. According to Todd's lawyers, Isis Agora Lovecruft wanted that Todd condemned some person she was accusing of rape publicly, which is an infamous trick to re-inforce a smear campaign: have a third-party condemning the alleged acts of some person before any charges are brought against that person and before any allegation verification goes through a due process with presumption of innocence and a fair trial. When Todd refused to condemn publicly that person (probably Kobeissi). Isis Agora Lovecruft accused EVEN Todd of rape and sexual assault: https://bitcoinwarrior.net/2019/04/former-bitcoin-core-developer-peter-todd-faces-rape-allegations-refutes-with-defamation-suit/ So Isis is accusing three different persons (Appelbaum, Kobeissi and Todd) of very serious crimes and currently none of them has had charges pressed against (so they did not even need to defend in a court, so far). Anyone who forgets presumption of innocence commits a paramount mistake that weakens human rights and strengthens the intelligence tactics based on smear campaigns since a century ago. The readiness through which some people in the "Western countries" are eager to forget the most fundamental rights is very dangerous and must be fought relentlessly, without any tiny hesitation. Further references: https://contraspin.co.nz/freeing-julian-assange-part-one/ Kind regards

Hello! It's a bug by Eddie which checks the IPv6 routes even with OpenVPN versions older than 2.4, when our servers refuse to push IPv6 to those versions. You have two available, alternative solutions: 1) Upgrade OpenVPN to version 2.4 or higher (latest stable version is 2.4.7). Recommended solution. 2) Alternatively, set the "IPv6 layer" combo box to "Block". You can find it in the "Preferences" > "Networking" window. You will renounce to IPv6 but Eddie will connect at least and you will not need to upgrade OpenVPN. Kind regards

@NormG1 Hello! It's just HTML5 geo-location: https://www.w3schools.com/html/html5_geolocation.asp HTML5 exists since 2014 and ipleak.net has this feature since then, so no news here. Do not enable HTML5 geo-location, or disable it if you have already done so. All browsers come with it disabled by default as far as we know. Kind regards