Hi,

On Fri, Apr 15, 2016 at 5:50 AM, Samuli Seppänen <sam...@openvpn.net> wrote:

> After a longish struggle I managed to produce a tap-windows6 driver that
> has SHA2 EV signature, and which installs correctly on one particular
> instance of Windows 7. An earlier driver signed with the same EV
> certificate loaded correctly on Windows 10.
>
> Now we'd need to verify that this particular driver installs and works
> correctly on other Windows versions, such as
>
> - Windows 10 (untested)
> - Windows 8.1 (untested)
> - Windows 7 (more testing is always good)
> - Windows Server 2012r2 (untested)
> - Windows Vista (untested, _might_ fail)
>

- Windows 10 (64 bit): success

Installs without error and works fine.

- Windows 7 (64 bit): success, but see below

Installs without error and works fine.
However, the driver details says that its _not_ digitally signed, but the
driver properties window shows "Digitally signed by OpenVPN Technologies
Inc."
Installing KB3123479 (update to support SHA2 signatures) makes no
difference.

- Windows server 2008r2 (64bit) : installs ok, but adapter fails

Installs without error, driver properties and driver details display same
as Windows 7 (i.e one says signed, other says not signed).
Cannot enable the tap adapter -- fails with the following error

"The TAP-Windows Adapter V9 service failed to start due to the following
error:
Windows cannot verify the digital signature for this file. A recent
hardware or software change might have installed a file that is signed
incorrectly or damaged, or that might be malicious software from an unknown
source."

On installing KB3123479, the error changes to
"The driver \Driver\tap0901 failed to load for the device ROOT\NET\0004."
and TAP adapters do no show up in the list of network adapters

- Windows vista (32 bit): installs after ignoring security warning, works
fine

Installation: Pops up a warning that says no valid signature, publisher not
verified etc. On choosing to install anyway, completes without error.
Tap adapter works fine

I thought driver signature is not enforced on 32 bit vista, but this is the
only platform (among those I tried) that complained loudly at installation
time.

Note: none of the above systems are up-to-date with windows updates.

Selva

Reply via email to