Re: [Openvpn-devel] Summary of the community meeting (15th April 2020) -- Win installer version checks
Hi, On Wed, Apr 15, 2020 at 11:52:50AM -0400, Nathan Stratton Treadway wrote: > (Of course, even better from a user standpoint would be a single unified > OpenVPN Windows installer which automatically installs the > correctly-signed drivers for the current system -- but I assume that > approach has already been investigated/considered earlier in the > development of the Windows installer) From my understanding, the upcoming 2.5 MSI installer should do this (a single .msi which contains all the individual packages needed for all plattforms and architectures). For the NSIS installer, this seems to be not so trivial, and since we wanted to move away from it anyway, nobody volunteered to implement and test it yet... but indeed, it would be nice to have, so *if* we have a volunteer, this would be certainly welcome :-) (*I* have no idea about windows installers, I'm a *BSD person) gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany g...@greenie.muc.de signature.asc Description: PGP signature ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
Re: [Openvpn-devel] Summary of the community meeting (15th April 2020) -- Win installer version checks
On Wed, Apr 15, 2020 at 13:38:37 +0300, Samuli Seppänen wrote: > > Here's the summary of the IRC meeting. > > --- > > COMMUNITY MEETING > > Place: #openvpn-meeting on irc.freenode.net > Date: Wed 15th April 2020 > Time: 11:30 CEST (09:30 UTC) > [...] > > Mattock will check if it would be possible to give unique identifiers to > Windows 7 and Windows 10 flavors of tap-windows6. This would prevent > situations where an existing, cached Windows 7 driver is preferred over > a Windows 10 (attestation signed) version, hence causing driver > installation failures. > > Mattock will also check if we could, with a reasonable effort, provide > users with an easy way to clean up old tap-windows6 drivers in the NSIS > installer. The process is already known and can be done with external > scripts, but integration / reimplementation in NSIS is missing. Just wanted to be sure that the separate-but-related step of having the Windows installer verify the Windows version at install time is also on the list for investigation. In our particular case, at least, if the Win7 installer had refused to proceed when executed under Win10, the situation with TAP driver mismatch would have been avoided completely. If it's possible to do, that seems a preferable outcome, even if the steps mentioned above also make it much easier to recover from the mismatch situation after the fact. (Of course, even better from a user standpoint would be a single unified OpenVPN Windows installer which automatically installs the correctly-signed drivers for the current system -- but I assume that approach has already been investigated/considered earlier in the development of the Windows installer) Thanks. Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
