Changes between Version 21 and Version 22 of BuildingTapWindows6
- Timestamp:
- 02/03/17 14:25:35 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildingTapWindows6
v21 v22 19 19 It is not clear if signtool's digest algorithm (/fd SHA|SHA256) affects the validity of the signature, or if the only important thing is the hash algorithm of the actual certificate. When the cross-certificates expires (in 5-15 years), an actual Microsoft signature is required in all drivers. This means that all drivers need to be submitted to Microsoft for signing (see links below for more information). 20 20 21 Due to the above, the build environment for tap-windows6 needs to setup just right:21 Due to the above, the build environment for tap-windows6 needs to be setup just right: 22 22 23 23 * Build computer should have WinDDK 7600.* installed, because currently buildtap.py does not work on anything newer. Build computer should have a SHA1 code-signing certificate in the certificate store under ''Currentuser\My''