Changes between Version 71 and Version 72 of BuildingOnWindows


Ignore:
Timestamp:
03/17/11 11:58:28 (13 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildingOnWindows

    v71 v72  
    234234}}}
    235235
    236 For details on the syntax see [http://msdn.microsoft.com/en-us/library/bfsktky3(v=vs.80).aspx Makecert.exe reference]; for more details look [http://msdn.microsoft.com/en-us/windows/hardware/gg487332 here].
     236For details on the syntax see [http://msdn.microsoft.com/en-us/library/bfsktky3(v=vs.80).aspx Makecert.exe reference]; for higher-level details look [http://msdn.microsoft.com/en-us/windows/hardware/gg487332 here].
    237237
    238238== Installing the test certificate to build and target computers ==
    239239
    240 Both build and target computers need to have the test certificate in their keystores. The ''build computer'' needs it for signing the driver catalog with ''signtool.exe''. The ''target computer'', on the other hand, needs to have the certificate installed to allow "trusting" it and loading it into the kernel.
     240Both build and target computers need to have the test certificate in their keystores. The ''build computer'' needs it for signing the driver catalog with ''signtool.exe''. The ''target computer'', on the other hand, needs to have the certificate installed or it won't trust the driver and won't allow loading it to the kernel.
    241241
    242242In both cases the certificate is imported using [http://msdn.microsoft.com/en-us/library/e78byta0%28v=vs.80%29.aspx certmgr.exe]:
     
    247247}}}
    248248
    249 Alternatively you can launch ''certmgr.exe'' without parameters and use the certificate import wizard. Although usage of ''certmgr.exe'' is straightforward, it is included (only?) in the massive [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=71deb800-c591-4f97-a900-bea146e4fae1&displaylang=en Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1] package.
     249You can also launch ''certmgr.exe'' without parameters and use the certificate import wizard. Although usage of ''certmgr.exe'' is straightforward, it is included (only?) in the massive [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=71deb800-c591-4f97-a900-bea146e4fae1&displaylang=en Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1] package, which you need to install.
    250250
    251251== Creating and signing the catalog file ==
     
    253253In order to sign the TAP-driver, you need to do three things:
    254254
     255 * Build OpenVPN and the TAP-driver
    255256 * Create a catalog definition (.cdf) file with a text editor
    256  * Create a catalog file with [http://msdn.microsoft.com/en-us/library/aa386967%28v=vs.85%29.aspx MakeCat.exe]
    257  * Sign the catalog file with [http://msdn.microsoft.com/en-us/library/8s9b9yaz%28v=vs.80%29.aspx Signtool.exe]
    258 
    259 The catalog definition file (e.g. tap.cdf) can be relatively simple:
     257 * Create a catalog file (.cat) from the .cdf with [http://msdn.microsoft.com/en-us/library/aa386967%28v=vs.85%29.aspx MakeCat.exe]
     258 * Sign the catalog file (.cat) with [http://msdn.microsoft.com/en-us/library/8s9b9yaz%28v=vs.80%29.aspx Signtool.exe]
     259
     260After building OpenVPN and TAP-drivers go to ''<openvpn-sources>/dist/amd64''. There you'll find ''tap0901.sys'' and ''OemWin2k.inf'' files. Create a catalog definition file (e.g. ''tap.cdf'') that look like this:
    260261
    261262{{{
    262263[CatalogHeader]
    263 
    264264Name=tap0901.cat
    265 
    266265PublicVersion=0x00000010
    267 
    268266ResultDir=.\
    269 
    270267EncodingType=
    271268
    272 
    273 
    274269[CatalogFiles]
    275 
    276270tap0901.inf=tap0901.sys
    277 
    278271OemWin2k.inf=OemWin2k.inf
    279272
    280273}}}
    281274
    282 Once the definition file is finished, copy ''tap0901.sys'' and ''OemWin2k.inf'' to the working directory and generate the real catalog file:
     275Make sure you have a linefeed at the end. Next generate the real catalog file using ''makecat'':
    283276
    284277{{{
     
    286279}}}
    287280
    288 Next you need to sign the catalog file:
     281Now sign the catalog file with ''signtool'':
    289282
    290283{{{
     
    293286
    294287As long as the test certificate has been imported using ''certmgr.exe'' (see above), this command should work.
     288
     289If you want, repeat this process for 32-bit version of the TAP-driver starting from ''<openvpn-sources>/dist/i386''.
    295290
    296291== Enabling test mode on target computer ==