Samuli Seppänen

It is not dual-signed (don't have the SHA1 key). But the driver file itself (tap0901.sys) now has a signature. Previously only the security catalog (tap0901.cat) had it.

I made the workaround installer official until I get the signature issue resolved. I submitted the tap-windows6 driver files to the Windows developer dashboard for signing, but I'm not sure...

The process for properly signing drivers for Windows 10 is quite convoluted. I will try to get the signing process sorted out by next week. Installers scripts will require changes...

Tap-windows 9.22.1 does not work on recent Windows 10 that has secure boot on and is a fresh install based on revision 1607 or later. This has everything to do...

This response comes a bit late, but anyways... you can put Windows into "Test mode" in which it accepts unsigned kernel drivers. That works at least on Windows 7, but...

Yes, it is possible. You should use the "windows-nsis" instead of "generic" directly. Our official builds are now MSI-based, but "windows-nsis" should still work fine - we still need it...

Well. I take that back. If you're building for Windows on Windows, I would recommend building with MSVC instead. We have a "msibuilder" VM in here that can be used...

@chipitsine : while we do produce [snapshot builds](https://github.com/OpenVPN/openvpn-windows-buildtest) already, I think having Travis build snapshots is a good idea. Especially as Travis can build the installers from PRs also. Such...

> Let's think if we need to maintain so called "generic" build system in this repo - it was used for making Windows releases, but nowadays we use msvc for...

@lygstate you can check what tap-windows6 version OpenVPN 2.4.x releases have used by checking the history of this file: https://github.com/OpenVPN/openvpn-build/blob/master/windows-nsis/build-complete.vars