How to build 11.10.1 Trusted storage toolkit.

[#1]

Summary

How to build 11.10.1 Trusted storage toolkit.

Synopsis

How to build 11.10.1 Trusted storage toolkit?

Discussion

Download and extract the toolkit for 11.10.1. Steps to build a trusted storage toolkit.

1. Update the lm_code.h, vendor & TRL keys and vendor name. Change lm_seeds (unique) for each vendor.
2. Update vendor daemon , publisher ID and Hash value under the platform directory --> ActivationSetting--> Publisher
3. Copy demo.rc file to vendor.rc and change to vendor name. It?s under platform directory.
4. Update the makefile.act with Vendor Daemon when building for trusted storage file.
5. Update a Demo with Vendor Daemon: machind\activation\prep_xml\vendor_daemon.xml
6. Update copy DemoTrustedConfigIn.xml to <vendor>TrustedConfigIn.xml ? physical environment <the platform_dir>/ publisher. Copy DemoTrustedConfigVmidIn.xml to <vendor>TrustedConfigInVmid.xml ? Virtual environment
7. Update <vendor>TrustedConfigIn.xml change <publisherId> element to your Publisher ID (from orders).
8. Update the eight <SeedPart> elements to unique seedpart.Under<vendor>TrustedConfigIn.xml. Save the file.
9. To encrypt the file run the following command on command prompt from <platform directory>/publisher:
   • tcencrypt -i <vendor>TrustedConfigIn.xml -o <vendor>TrustedConfigOut.xml -k <vendor>KeyFile.xml

Output will be:

Processing complete, config output written to file <vendor>TrustedConfigOut.xml Key output written to file <vendor>KeyFile.xml

1. Sign <vendor>TrustedConfigOut.xml created in above step. To do so, run the following command on command prompt from <platform directory>/publisher:
   • xmlsign -a ../ActivationSettings/publisher.xml -i <vendor>TrustedConfigOut.xml -o <vendor>TrustedConfigOut.xml

The following output is displayed:

<vendor>TrustedConfigOut.xml signed.

1. Copy <platform_dir>/publisher/<vendor>Keyfile.xml to <platform_dir>/publisher/xml and then delete <platform_dir>/publisher/xml/DemoKeyout.xml this will replace the Demo configuration key file with publisher-specific. (File is used for Manual Response Generator.)
2. For Virtual environment repeat from step 11 for <vendor>TrustedConfigVmidIn.xml in step 12 to 14, output file will be <vendor>TrustedConfigVmidOut.xml and <vendor>KeyFileVmid.xml.
3. To update the preptool configuration files for client side and server side activation utilities:
   • Server side: Under <install_dir>examples-->activation -->serverActUtil.xml

Update :

<trustedconfiguration path="publisher/<demo>TrustedConfigOut.xml" policy="Physical" />
<trustedconfiguration path="publisher/<demo>TrustedConfigVmidOut.xml" policy="Virtual"/>

Change demo to your Vendor Daemon.

• Client side: Under <install_dir>examples-->activation--> appActUtil.xml

Update :

<trustedconfiguration path="publisher/<vendor>TrustedConfigOut.xml" policy="Physical" />

<trustedconfiguration path="publisher/<demo>TrustedConfigVmidOut.xml" policy="Virtual" />

Change demo to your Vendor Daemon

1. Under <install_dir>examples -->activation -->Comptranutil -->appCompTranUtil(Application side)

Update :

<trustedconfiguration path="publisher/<demo>TrustedConfigOut.xml" policy="Physical" />

<trustedconfiguration path="publisher/<demo>TrustedConfigVmidOut.xml" policy="Virtual" />

Change demo to your Vendor Daemon

1. Under --><install_dir>examples activation -->Comptranutil -->CompTranUtil (Server side)

Update :

<trustedconfiguration path="publisher/<demo>TrustedConfigOut.xml" policy="Physical"/>

<trustedconfiguration path="publisher/<demo>TrustedConfigVmidOut.xml" policy="Virtual"/>
Change demo to your Vendor Daemon

Save and close.

1. Now build the toolkit using the command nmake ?f makefile.act from platform directory.