can be created with standard, non-EV authenticode keys on all platforms. The user-mode signatures for openvpn.exe, openvpnserv.exe etc. So we have the following architecture-signature combinations for tap-windows6: We not only have the architecture split (i386, 圆4, amd64), but also different types of kernel-mode signatures for tap-windows6: There are several "targets" for the installer. The documentation and instructions for developers on components, their functions and relationship should be published on Wiki and/or in the openvpn-build readme.The documentation and instructions on how to deploy, transform, or parameterize MSI packages should be published on Wiki and/or in the openvpn-build readme.The MSI should consume the artefacts that the openvpn-build cross-compile process produces. The MSI (WiX) code can be placed into a subdirectory in openvpn-build Git repository alongside "generic", "msvc" and "windows-nsis".Having it in tap-windows6 repository would make signing that DLL slightly more problematic, as we don't really sign anything with the tap-windows6 buildsystem anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |