TA Binary Confidentiality and Completeness

4.1.5

Verify that the TA binary file is confidential and complete.

See Test Networking.

1. The TrustZone kit has been burnt into the server and the TrustZone license has been activated.
2. The TrustZone REE patch has been loaded to the server. The CA and TA can be loaded and can communicate with each other properly.

1. Log in to the REE OS and load the TrustZone REE patch. (See Expected Result 1.)

   insmod tzdriver

   /usr/bin/teecd &

2. Run the test CA and TA. (See Expected Result 2.)
3. Replace the preset public key in the iTrustee SDK. Compile, deploy, and run the test CA and TA again. (See Expected Result 3.)
4. Use the original preset public key of the iTrustee SDK again and replace the config binary file of the TA. Then compile, deploy, and run the test CA and TA again. (See Expected Result 4.)
5. Use the original config binary file of the TA again and replace the private key of the TA signature. Then compile, deploy, and run the test CA and TA again. (See Expected Result 5.)
6. Use the correct private key of the TA signature again, modify the manifest.txt file, and increase the value of the dataSize field for the TA heap space. Then compile, deploy, and run the test CA and TA again. (See Expected Result 6.)
7. Replace the manifest.txt file with the correct one and increase the OS time in the REE by at least 10 years. Then compile, deploy, and run the test CA and TA again. (See Expected Result 7.)

1. The REE patch is loaded and no error information is displayed.
2. The test CA and TA are running properly and no error information is displayed. The terminal output and tlogcat security log output meet the expected output of the test CA and TA.
3. The TA fails to be loaded and the tlogcat security log indicates that the TA decryption fails.
4. The TA fails to be loaded and the tlogcat security log indicates that the config signature verification fails.
5. The TA fails to be loaded and the tlogcat security log indicates that the config signature verification fails.
6. The TA fails to be loaded and the tlogcat security log indicates that the TA permission matching fails.
7. The TA fails to be loaded and the tlogcat security log indicates that the TA certificate is invalid.