However, I don't know if you have a W10 system lying around to test, but if I want to change the driver for this COM port device, unticking the 'Show compatible hardware' checkbox won't let me select the RNDIS built-in driver.It's possible Windows enacts some kind of enforcement and won't allow to set the driver for some unknown VID/PID couple. Thanks for the feedback have pulled the zip archive and published a second version of the package.To me it's not as huge an issue as stated because the private key is passphrased with a long enough password, but I understand what you mean and generated a fresh set of keys to sign the driver and did not distribute the private key this timeAs for it being the normal procedure, that's what I thought before I actually tried I previously 'forced' the RNDIS driver for a tethered android phone in Windows 7 and it worked. v Print verbose success and status messages.Īn alternative to comodo timestamping (untested). sign - Sign files using an embedded signature. Code: 'C:EWDKProgram FilesWindows Kits10binx86signtool.exe' sign /v ^/f MobileRead-CodeSigning-CA.pfx ^/fd sha256 /tr /td sha256 ^kindlerndisamd64.cat.
Code: 'C:EWDKProgram FilesWindows Kits10binx86pvk2pfx.exe' ^-pvk MobileRead-CodeSigning-CA.pvk -spc MobileRead-CodeSigning-CA.cer ^-f -pfx MobileRead-CodeSigning-CA.pfxThis command combines your keypair in a single passphrased pfx (analogue to a ).pvk - input PVK file name.spc - input SPC file - force overwrite existing PFX file.pfx - output PFX file name.【Signing the Driver】It's a two-stage operation: enumerate files into a catalog (.cat), sign the catalog.Step 3, '3-buildcat.cmd' will inspect the INF file and produce a catalog of signed files. You can download it at after accepting the EULA.After obtaining the kit, extract it to C:EWDK.We actually only need a very very small subset of the kit, in C:EWDKProgram FilesWindows Kits10binx86 (50 MiB out of 1.5 GiB), maybe we could only fetch the relevant parts of the ZIP remotely like some do at reboot.pro/ but it is out of scope of this tutorial.Open '1-createCA.cmd' in a text editor. (Recent example, )Requirements are the driver package in first post, and the Enterprise WDK from Microsoft.
0 kommentar(er)
