Changes between Version 1 and Version 2 of BuildingTapWindows6

04/19/16 09:02:57 (6 years ago)
Samuli Seppänen

Add some notes regarding codesigning


  • BuildingTapWindows6

    v1 v2  
    1 Build instructions for tap-windows6 [ are available] in it's Git repo.
     1= Introduction =
     3The build instructions for tap-windows6 [ are available] in it's Git repo. This page contains additional information that is more generic and not really suitable for inclusion in the main documentation.
     5= Codesigning =
     7Getting the [ Authenticode signatures] right so that all Windows versions detect them can be quite tricky. This seems to be particularly true for kernel-mode driver packages. This section contains miscellaneous notes about signing driver packages.
     9== Working with certificates and signatures in Powershell ==
     11To install a PFX files to the CurrentUser certificate store:
     13Import-PfxCertificate –FilePath <path-to-pfx> cert:\CurrentUser\My -Password (ConvertTo-SecureString -String "mypassword" -Force –AsPlainText)
     16To verify the Authenticode signature of a file:
     19Get-AuthenticodeSignature <path-to-file>
     21Note that even if the above command says that the file's certificate is valid, there is absolutely no guarantee that various Windows versions will accept it. It is unclear whether the Cmdlet checks the entire certificate path or not: it does hang for long periods of time occasionally doing ''something''.
     23== Using Signtool.exe ==
     25Verifying the signature of a driver package using Signtool.exe:
     27signtool verify /v /kp /c tap901.sys
     29This command should produce more useful results than the Get-AuthenticodeSignature Cmdlet.