Leaderboard

Google authenticator with my phone number for 2FA? These are huge red flags that tells me AirVPN is not what they say they are i.e. secure and anonymous. Quite the contrary. Maybe even part of the great social engineering clik. No thanks. Glad I diden't actually buy a subscription.

In your fantasy world only. In AirVPN 2FA is based on TOTP https://en.wikipedia.org/wiki/Time-based_one-time_password which does not require any Google app and does not require any phone number. TOTP is an open protocol described by IETF in RFC 6238

Hello! The alien VPN interface causes a critical error to OpenVPN. Please see here for a quick and effective solution: https://airvpn.org/forums/topic/56643-stuck-in-a-broken-route-never-connects/?do=findComment&comment=225323 Kind regards

Hello! In 2019 we pushed a commit with a major new feature for OpenVPN3 library but it was refused by the maintainer (Arne Schwabe) for stylistic reasons. In the opinion of some of us it's their (OpenVPN3 maintainers) style to be ugly, but OK it's a matter of personal tastes so the text format and spacing was changed accordingly and a new commit was ready. The new commit was again refused, this time because the source code included tags mentioning the source code author "ProMIND". We couldn't fully understand why the author should not be mentioned in the source code itself, moreover the tags were useful for another purpose, but fine, all tags were removed and a new commit was ready. The new commit was again refused, this time because the identity of the source code author ProMIND was not certified. In general we do not disclose the identity of our employees and collaborators, much less force them to certify it with any third party, and leave to them the choice to disclose real identity and certify it. The request was strange and we asked for some clarification. It came out, even from other OpenVPN community members, that the requirement was related to a specific contractual agreement mentioned here: https://github.com/OpenVPN/openvpn3/blob/master/CLA.rst At that point we did not like the situation: please note that a new problem was mentioned only after each new commit was proposed, while it would have been fair that all problems were mentioned at the same time, obviously, since the very beginning. And we did not like anymore to allow OpenVPN Inc. to re-license under any new license our or ProMIND's code, which is under GPLv3, according to the mentioned contributor's agreement, specifically part II, (e) clause: "(e) I understand that OpenVPN Inc. may relicense this project, this contribution, and any modification to it under any license. [...]". Therefore we did not waste additional time on the matter and we went on with our fork without further ado. At this very moment we have no merging/commit plans. On a lighter tone, this thread dated 2019 is funny in the last part: https://airvpn.org/forums/topic/43850-openvpn-3-development/ because one of the AirVPN community moderators defended OpenVPN style and Schwabe refusals, and wrote: "If you had contributed to the Linux kernel like that, Linus would tear you to tiny bits." Ironically, after that message was written, Linus Torvalds examined OpenVPN code and he was horrified. Kind regards