WireGuard Windows Client Controversy





Before I even begin my testing of the WireGuard protocol, there is already a controversial issue which I need to address.





As of yet, there is no official Windows client released by the WireGuard team.





I am going to be using the Tunsafe client for Windows, which is made by a third party.







On the official WireGuard website, there is a warning about using this client.





A Windows client is coming soon. In the meantime, you are strongly advised to stay away from Windows clients that are not released from this site, as they may be dangerous to use, despite marketing efforts.





Here is an interesting thread on Reddit, where the author of WireGuard warns people not to use Tunsafe because it's closed-source.





As the author of WireGuard, I'd STRONGLY advise against using this closed-source implementation, which likely has interoperability and security issues.

We'll have an official Windows client coming out shortly, which won't have these same security concerns.





I should note that despite this thread being a year old and the author stating "We'll have an official Windows client coming out shortly", there is still no official Windows client released at this time.





In this same thread, the author of the Tunsafe client responds.





As the author of TunSafe and µTorrent, I wonder if you base that statement on facts or is it just an attempt at spreading FUD and general dislike against non open-source applications?

The official Windows client you mention is far from complete and nothing but an unsupported research project right now.

Your Go repo says: "There is no group of users that should be using the code in this repository here under any circumstances at the moment, not even beta testers or dare devils. It simply isn't complete."



Fast forward to 5 months later, in another Reddit thread, it was announced that the Tunsafe client was made open source.





The author of WireGuard responds to this thread.





I too would have loved to work together, but he seemed pretty adamant about going off in the hostile direction. Bummer.





To which the Tunsafe author responded.





I still don't understand your viewpoint that everything that's not under your umbrella is hostile. Never at any point was I hostile in discussions with you. You should be happy that people embrace your fantastic protocol instead of having a negative attitude.







It seems like there are some personal issues between the WireGuard author and the Tunsafe client author. Despite the fact that Tunsafe was made open source, the warning against using it remains on the WireGuard website.





Please do your own research and decide whether you think the Tunsafe Windows client is safe to use or not. Personally, I am using it and I don't have any concern about it.





If you are not using Windows, here are the official WireGuard clients that you can use.







WireGuard for Mac

WireGuard for Android

WireGuard for iOS

WireGuard for Linux





#1 WireGuard provider - 12VPN







I'm not surprised to see that WireGuard is available with 12VPN. They are always offering the latest alternative protocols such as Shadowsocks, Outline, Openconnect, v2Ray, etc.





The only problem I had setting up WireGuard with 12VPN is that they don't offer any setup instructions for Windows.