Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Samuli Seppänen]

Hi,

Il 18/04/2018 20:22, Selva Nair ha scritto:
> 
> Hi,
> 
> On Tue, Apr 17, 2018 at 3:01 AM, Samuli Seppänen  > wrote:
> 
> 
> 
> Excellent and thanks for testing! This gives me a lot more confidence in
> the Authenticode signature.
> 
> 
> I don't want to question that as none of my Windows hosts complains
> about the signature. But the driver details tab shows the file as not
> digitally signed. That's as in, adapter properties -> driver -> driver
> details. One level before that it shows Digital signer: OpenVPN Tech..
> Go figure.. And likely this "problem" existed in previous version too.
> This is on Windows 7.

This has always been the same afaik. I think it is an inconsistency in
how Windows checks the signature.

> Looking into this further using pnputil and sigverify:
> 
> C:\Windows\System32>pnputil -e
> Microsoft PnP Utility
> 
> .. snipped...
> 
> Published name :    oem13.inf
> Driver package provider :   Microsoft
> Class : Printers
> Driver date and version :   05/28/2012 15.0.4128.4000
> Signer name :   Microsoft Windows Hardware Compatibility
> Publisher
> 
> Published name :    oem14.inf
> Driver package provider :   TAP-Windows Provider V9
> Class : Network adapters
> Driver date and version :   04/13/2018 9.00.00.21
> Signer name :
> 
> ...snipped...
> 
> C:\Windows\System32\catroot>  sigverify
> 
> This also lists tap0901.sys as unsigned.
> 
> Is this a known Windows 7 issue? Will check Windows 10 later tonight.
> 
> Selva

I believe it is enough if the catalog file is signed. If my memory
serves me correctly the sys file could be signed at some point in the
history of Windows.

If you can test 64-bit Windows 10 with Secure boot enabled which is not
an upgrade from Windows 7/8 that would be optimal. I've been told that
combo is the most picky about signatures.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Selva Nair]

Hi,

On Tue, Apr 17, 2018 at 3:01 AM, Samuli Seppänen  wrote:

>
>
> Excellent and thanks for testing! This gives me a lot more confidence in
> the Authenticode signature.
>

I don't want to question that as none of my Windows hosts complains about
the signature. But the driver details tab shows the file as not digitally
signed. That's as in, adapter properties -> driver -> driver details. One
level before that it shows Digital signer: OpenVPN Tech.. Go figure.. And
likely this "problem" existed in previous version too. This is on Windows 7.

Looking into this further using pnputil and sigverify:

C:\Windows\System32>pnputil -e
Microsoft PnP Utility

.. snipped...

Published name :oem13.inf
Driver package provider :   Microsoft
Class : Printers
Driver date and version :   05/28/2012 15.0.4128.4000
Signer name :   Microsoft Windows Hardware Compatibility
Publisher

Published name :oem14.inf
Driver package provider :   TAP-Windows Provider V9
Class : Network adapters
Driver date and version :   04/13/2018 9.00.00.21
Signer name :

...snipped...

C:\Windows\System32\catroot>  sigverify

This also lists tap0901.sys as unsigned.

Is this a known Windows 7 issue? Will check Windows 10 later tonight.

Selva
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Selva Nair]

Hi,

On Wed, Apr 18, 2018 at 2:58 AM, Gert Doering  wrote:

> On Tue, Apr 17, 2018 at 09:45:24PM -0400, Selva Nair wrote:
> > (ii) The driver version shows up as 9.0.0.21 -- this is apparently taken
> > from the inf file. Why is it not 9.21.3? The file version is 9.21.3 9/21
> as
> > expected.
>
> I have no idea how the various values in version.m4 should work.  There
> are many numbers...
>
> What I have (after bumping all "21" to "22", and ".2/.3" to ".1") is:
>
> define([PRODUCT_NAME], [TAP-Windows])
> define([PRODUCT_PUBLISHER], [OpenVPN Technologies, Inc.])
> define([PRODUCT_VERSION], [9.22.1])
> define([PRODUCT_VERSION_RESOURCE], [9,0,0,22])
> define([PRODUCT_TAP_WIN_COMPONENT_ID], [tap0901])
> define([PRODUCT_TAP_WIN_MAJOR], [9])
> define([PRODUCT_TAP_WIN_MINOR], [22])
> define([PRODUCT_TAP_WIN_REVISION], [1])
> define([PRODUCT_TAP_WIN_BUILD], [601])
>
> So, no idea what PRODUCT_VERSION_RESOURCE does and why it is not "9,22,1,0"
> (or the like).
>

These are custom defines, so it depends on how those variables are used in
the resource file and the inf file.

The relevant defines in resource.rc are

VER_PRODUCTVERSION = major,0,0,minor --> 9,0,0,22
VER_PRODUCTVERSION_STR = "PRODUCTVERSION" "major/minor" --> "9.22.1 9/22"
(no idea why that 9/22 is added or build is not included).

The driver inf (OemVista.inf.in) file defines the driver version as
major,0,0,minor which matches the product version above.

Currently PRODUCT_VERSION_RESOURCE as such and revision, build numbers are
unused.

I have no idea whether there are any implications of changing the version
in two places (resource and inf) consistently  to major,minor,release,build.

Selva
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[fragmentux]

On 18/04/18 08:19, Samuli Seppänen wrote:

Hi,

A couple of follow-up questions from a fellow tap-windows6 builder:

- Is you Windows 10 system a clean install (not upgraded from 7/8)?


This system was upgraded from Win 7


- Is secure boot turned on?


No .. no UEFI


- Is your Windows 10 64-bit?


Yes



If the answer to all of these is "yes" then I think we're pretty safe as
far as the signature is concerned.



Considering my last update was over 6GB it is hard to accept that this
really is w10 ;-)

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Samuli Seppänen]

Hi,

Il 18/04/2018 09:58, Gert Doering ha scritto:
> Hi,
> 
> On Tue, Apr 17, 2018 at 09:45:24PM -0400, Selva Nair wrote:
>> (ii) The driver version shows up as 9.0.0.21 -- this is apparently taken
>> from the inf file. Why is it not 9.21.3? The file version is 9.21.3 9/21 as
>> expected.

I think the confusing versioning is just historic baggage which we have
never bothered to fix.

> I have no idea how the various values in version.m4 should work.  There
> are many numbers...
> 
> What I have (after bumping all "21" to "22", and ".2/.3" to ".1") is:
> 
> define([PRODUCT_NAME], [TAP-Windows])
> define([PRODUCT_PUBLISHER], [OpenVPN Technologies, Inc.])
> define([PRODUCT_VERSION], [9.22.1])
> define([PRODUCT_VERSION_RESOURCE], [9,0,0,22])
> define([PRODUCT_TAP_WIN_COMPONENT_ID], [tap0901])
> define([PRODUCT_TAP_WIN_MAJOR], [9])
> define([PRODUCT_TAP_WIN_MINOR], [22])
> define([PRODUCT_TAP_WIN_REVISION], [1])
> define([PRODUCT_TAP_WIN_BUILD], [601])
> 
> So, no idea what PRODUCT_VERSION_RESOURCE does and why it is not "9,22,1,0"
> (or the like).
> 
> It would certainly make things easier if that would output the same
> number in all places.

Agreed. I would love to bump 9,0,0,21 into 9,22,1,601. I _think_ Windows
should be fine with that. We can discuss this in today's meeting.

> 
> 
>> (iii) On Win7, the interface gets metric 20 --- implying a speed < 200 Mbps
>> as per the Windows automatic metric assignment table. Isn't this supposed
>> to get detected as a 1Gbps adapter now? The link speed patch is in master
>> and this one is one point ahead of it (9.21.3), so expected to see it here.
> 
> The test driver is based on master before the link speed patch, with an
> independent version bump.  Sorry for that confusion.
> 
> gert
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> 
> 
> 
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
> 


-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Samuli Seppänen]

Hi,

A couple of follow-up questions from a fellow tap-windows6 builder:

- Is you Windows 10 system a clean install (not upgraded from 7/8)?
- Is secure boot turned on?
- Is your Windows 10 64-bit?

If the answer to all of these is "yes" then I think we're pretty safe as
far as the signature is concerned.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

Il 16/04/2018 16:56, fragmentux ha scritto:
> Hi,
> 
> I have successfully installed and am currently using this driver
> on Windows 10 fully upto date.
> 
> Aside from the usual windblows crap (new layers of BS between *Programs
> and Features and Network Connections .. you know what I mean) the
> installation went smoothly.
> 
> However, some issues encountered:
> 
> * On first running my normal (unchanged) server config, openvpn bombed
> out with "Cannot retrieve password" .. on second run the error was gone.
> Tried uninstall/reinstall TAP driver and the same error did NOT occur.
> 
> * During install Windows asked "If i wanted to trust openvpn inc .."
> to which I replied NO.  On the second install Windows did NOT ask "if
> I wanted to trust openvpn inc." .. I don't know what that means ..
> Perhaps, the install cert was installed anyway ?
> 
> HTH
> 
> 
> 
> 
> On 16/04/18 08:20, Samuli Seppänen wrote:
>> Hi,
>>
>> We're bundling a tap-windows6 driver (9.21.3) with OpenVPN 2.4.6 that is
>> due later this week:
>>
>> https://build.openvpn.net/downloads/temp/tap-windows-9.21.3-I601.exe
>>
>> The main difference to the old driver (9.21.2) is that the driver and
>> installer have only a SHA2 Authenticode signature[*]. This means that
>> Windows Vista should refuse to install the driver. Some outdated Windows
>> 7 installations might behave the same. This is intentional on our part,
>> as Vista is EOL and we don't want to support Windows 7 installations
>> that are horribly outdated.
>>
>> I've tested installing this driver on Windows 7 Pro (64-bit) and Windows
>> 2012r2 (64-bit) and I did not encounter any installation issues.
>> However, I do not have access to Windows 8 or Windows 10, nor to 32-bit
>> platforms.
>>
>> I would appreciate somebody could do additional driver installation
>> tests. This would help build confidence in the driver before we push it
>> out. Verifying that the driver installs fine is enough.
>>
>>
>>
>> --
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Openvpn-devel mailing list
>> Openvpn-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>>
> 
> --
> 
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Gert Doering]

Hi,

On Tue, Apr 17, 2018 at 09:45:24PM -0400, Selva Nair wrote:
> (ii) The driver version shows up as 9.0.0.21 -- this is apparently taken
> from the inf file. Why is it not 9.21.3? The file version is 9.21.3 9/21 as
> expected.

I have no idea how the various values in version.m4 should work.  There
are many numbers...

What I have (after bumping all "21" to "22", and ".2/.3" to ".1") is:

define([PRODUCT_NAME], [TAP-Windows])
define([PRODUCT_PUBLISHER], [OpenVPN Technologies, Inc.])
define([PRODUCT_VERSION], [9.22.1])
define([PRODUCT_VERSION_RESOURCE], [9,0,0,22])
define([PRODUCT_TAP_WIN_COMPONENT_ID], [tap0901])
define([PRODUCT_TAP_WIN_MAJOR], [9])
define([PRODUCT_TAP_WIN_MINOR], [22])
define([PRODUCT_TAP_WIN_REVISION], [1])
define([PRODUCT_TAP_WIN_BUILD], [601])

So, no idea what PRODUCT_VERSION_RESOURCE does and why it is not "9,22,1,0"
(or the like).

It would certainly make things easier if that would output the same
number in all places.


> (iii) On Win7, the interface gets metric 20 --- implying a speed < 200 Mbps
> as per the Windows automatic metric assignment table. Isn't this supposed
> to get detected as a 1Gbps adapter now? The link speed patch is in master
> and this one is one point ahead of it (9.21.3), so expected to see it here.

The test driver is based on master before the link speed patch, with an
independent version bump.  Sorry for that confusion.

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
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Selva Nair]

Hi,

A couple of things I noticed

(i) On a slightly outdated Windows 7 box (last update in Sep 2017),
previously running 2.4.5, the install appeared to succeed but the tap
adapter was no longer usable -- openvpn errors out with CreateFile()
failure when opening the adapter. Reinstalling or recreating the adapters
did not work. Evenlog showed

Fault bucket , type 0
Event Name: PnPDeviceProblemCode
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: tap0901
P3: {4d36e972-e325-11ce-bfc1-08002be10318}

Anyway, on bringing the system up to date,  reinstalling fixed it. Probably
a one-off thing or gremlins So much for that.

(ii) The driver version shows up as 9.0.0.21 -- this is apparently taken
from the inf file. Why is it not 9.21.3? The file version is 9.21.3 9/21 as
expected.

(iii) On Win7, the interface gets metric 20 --- implying a speed < 200 Mbps
as per the Windows automatic metric assignment table. Isn't this supposed
to get detected as a 1Gbps adapter now? The link speed patch is in master
and this one is one point ahead of it (9.21.3), so expected to see it here.

Not even (i) may be related to the signature, so the use of sha256 digest
looks like a non-issue.

Selva
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Samuli Seppänen]

Hi,

Il 16/04/2018 16:56, fragmentux ha scritto:
> Hi,
> 
> I have successfully installed and am currently using this driver
> on Windows 10 fully upto date.
> 
> Aside from the usual windblows crap (new layers of BS between *Programs
> and Features and Network Connections .. you know what I mean) the
> installation went smoothly.
> 
> However, some issues encountered:
> 
> * On first running my normal (unchanged) server config, openvpn bombed
> out with "Cannot retrieve password" .. on second run the error was gone.
> Tried uninstall/reinstall TAP driver and the same error did NOT occur.

I think this was some glitch. The "Cannot retrieve password" does not
seem tap-related at all.

> * During install Windows asked "If i wanted to trust openvpn inc .."
> to which I replied NO.  On the second install Windows did NOT ask "if
> I wanted to trust openvpn inc." .. I don't know what that means ..
> Perhaps, the install cert was installed anyway ?

Perhaps it cached the answer in memory, but not on disk? In any case the
signature seems solid even on fully up-to-date Windows 10.

Many thanks for testing this!

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock


> 
> HTH
> 
> 
> 
> 
> On 16/04/18 08:20, Samuli Seppänen wrote:
>> Hi,
>>
>> We're bundling a tap-windows6 driver (9.21.3) with OpenVPN 2.4.6 that is
>> due later this week:
>>
>> https://build.openvpn.net/downloads/temp/tap-windows-9.21.3-I601.exe
>>
>> The main difference to the old driver (9.21.2) is that the driver and
>> installer have only a SHA2 Authenticode signature[*]. This means that
>> Windows Vista should refuse to install the driver. Some outdated Windows
>> 7 installations might behave the same. This is intentional on our part,
>> as Vista is EOL and we don't want to support Windows 7 installations
>> that are horribly outdated.
>>
>> I've tested installing this driver on Windows 7 Pro (64-bit) and Windows
>> 2012r2 (64-bit) and I did not encounter any installation issues.
>> However, I do not have access to Windows 8 or Windows 10, nor to 32-bit
>> platforms.
>>
>> I would appreciate somebody could do additional driver installation
>> tests. This would help build confidence in the driver before we push it
>> out. Verifying that the driver installs fine is enough.
>>
>>
>>
>> --
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Openvpn-devel mailing list
>> Openvpn-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>>
> 
> --
> 
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Samuli Seppänen]

Il 16/04/2018 16:43, Simon Rozman ha scritto:
>> I've tested installing this driver on Windows 7 Pro (64-bit) and Windows
>> 2012r2 (64-bit) and I did not encounter any installation issues.
>> However, I do not have access to Windows 8 or Windows 10, nor to 32-bit
>> platforms.
>>
>> I would appreciate somebody could do additional driver installation tests.
>> This would help build confidence in the driver before we push it out.
>> Verifying that the driver installs fine is enough.
> 
> Windows 7 - upgrades OK, OpenVPN works without issues
> Windows 8.1 - installs OK, TUN/TAP interface creates OK
> Windows Server 2016 build 1607 - upgrades OK, OpenVPN works without issues
> 
> Best regards,
> Simon
> 

Excellent and thanks for testing! This gives me a lot more confidence in
the Authenticode signature.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[fragmentux]

Hi,

I have successfully installed and am currently using this driver
on Windows 10 fully upto date.

Aside from the usual windblows crap (new layers of BS between *Programs 
and Features and Network Connections .. you know what I mean) the

installation went smoothly.

However, some issues encountered:

* On first running my normal (unchanged) server config, openvpn bombed
out with "Cannot retrieve password" .. on second run the error was gone.
Tried uninstall/reinstall TAP driver and the same error did NOT occur.

* During install Windows asked "If i wanted to trust openvpn inc .."
to which I replied NO.  On the second install Windows did NOT ask "if
I wanted to trust openvpn inc." .. I don't know what that means ..
Perhaps, the install cert was installed anyway ?

HTH




On 16/04/18 08:20, Samuli Seppänen wrote:

Hi,

We're bundling a tap-windows6 driver (9.21.3) with OpenVPN 2.4.6 that is
due later this week:

https://build.openvpn.net/downloads/temp/tap-windows-9.21.3-I601.exe

The main difference to the old driver (9.21.2) is that the driver and
installer have only a SHA2 Authenticode signature[*]. This means that
Windows Vista should refuse to install the driver. Some outdated Windows
7 installations might behave the same. This is intentional on our part,
as Vista is EOL and we don't want to support Windows 7 installations
that are horribly outdated.

I've tested installing this driver on Windows 7 Pro (64-bit) and Windows
2012r2 (64-bit) and I did not encounter any installation issues.
However, I do not have access to Windows 8 or Windows 10, nor to 32-bit
platforms.

I would appreciate somebody could do additional driver installation
tests. This would help build confidence in the driver before we push it
out. Verifying that the driver installs fine is enough.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] New tap-windows6 driver (9.21.3) available for testing

[Simon Rozman]

> I've tested installing this driver on Windows 7 Pro (64-bit) and Windows
> 2012r2 (64-bit) and I did not encounter any installation issues.
> However, I do not have access to Windows 8 or Windows 10, nor to 32-bit
> platforms.
> 
> I would appreciate somebody could do additional driver installation tests.
> This would help build confidence in the driver before we push it out.
> Verifying that the driver installs fine is enough.

Windows 7 - upgrades OK, OpenVPN works without issues
Windows 8.1 - installs OK, TUN/TAP interface creates OK
Windows Server 2016 build 1607 - upgrades OK, OpenVPN works without issues

Best regards,
Simon


smime.p7s
Description: S/MIME cryptographic signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel