-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all,
People have encountered a few rather serious issues with OpenVPN 2.3.x for Windows. These issues only materialize when one is using OpenVPN 2.3.x with tap-windows6: <https://community.openvpn.net/openvpn/ticket/430> <https://community.openvpn.net/openvpn/ticket/432> The underlying issue is that OpenVPN 2.3.x does not handle return code 995 from tap-windows6 at all. According to the driver author most s.c. tap-windows6 issues stem from this single omission in OpenVPN 2.3.x itself. There are now tentative fixes for the 995 issue here: <https://github.com/TDivine/openvpn/commit/c391f10e79d88d01405eedbc6822bc92cf8a210d> <https://github.com/TDivine/openvpn/commit/44b56c14c66201074805a4c5b97da2cfb1e1f248> However, those fixes are for the Git "master" branch, which cannot currently be built using "openvpn-build" (i.e. for Windows). A few weeks ago I backported the above patches to OpenVPN 2.3.4 and released test installers[1] which apparently fixed the primary issue[2]. Do we / can we merge the patches to "master" without testing based on the fact that they worked for OpenVPN 2.3.4? We'd also need to backport these fixes to 2.3 and make a new release. Looks like there's quite a lot of stuff in the pipe for 2.3.5, so it probably makes sense to release all of it along with these tap-windows6-related fixes in one go. Anything blocking 2.3.5 release atm? - -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock [1] <http://swupdate.openvpn.org/community/releases/openvpn-install-2.3.4-I603-i686.exe> <http://swupdate.openvpn.org/community/releases/openvpn-install-2.3.4-I603-x86_64.exe> [2] <https://community.openvpn.net/openvpn/ticket/430#comment:11> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlREzmUACgkQwp2X7RmNIqNguACeLDF/720Obl6IrNNs0OWYU88N 6GoAn3PQSgxKX+M2UxY6WJKujLXtOTOI =Xb+t -----END PGP SIGNATURE-----
