Compiling and Running the Project
- Modify RSA_CRYPTO_uuid and RSA_CRYPTO_DEMO_TA_PATH in the src/RSA/CA/rsa_ca_demo.c file.
- Change RSA_CRYPTO_uuid to the UUID of the developer certificate. The following is an example.
1 2 3 4 5
/* RSA CRYPTO DEMO uuid: f68fd704-6eb1-4d14-b218-722850eb3ef0 */ static const TEEC_UUID RSA_CRYPTO_uuid = { 0xf68fd704, 0x6eb1, 0x4d14, { 0xb2, 0x18, 0x72, 0x28, 0x50, 0xeb, 0x3e, 0xf0 } };
- Change RSA_CRYPTO_DEMO_TA_PATH to /data/uuid.sec.
#define RSA_CRYPTO_DEMO_TA_PATH "/data/uuid.sec"
- Change RSA_CRYPTO_uuid to the UUID of the developer certificate. The following is an example.
- Change the absolute paths of the developer private key file and config file in ./TA/cloud/config_cloud.ini.
- Change the value of secSignKey to the absolute path of private_key.pem.
- Change the value of configPath to the absolute path of config.
Figure 1 Changing the file paths
- Access the Kunpeng DevKit, click the Development tab and then the Compile button in the Compiler and Debugger area to perform compilation. See Figure 2.
- After the compilation is complete, click
in the upper right corner of the page. On the displayed page, choose General Settings > Target Server Management. Then click Log In in the Operation column of the target server to log in. See Figure 3. - View the compilation result.
1 2
cd /vendor/bin/ ll

- Run the demo.
1/vendor/bin/rsa_demo
Figure 4 Running the demo
- Click
in the upper right corner of the page, choose Project Settings, and click the Compile tab. On the displayed page shown in Figure 5, modify the compilation configuration parameters, click Save, and then click Compile to compile the project again.


