TrustedFirmware Git Browser
Code Review Sign In
review.trustedfirmware.org / OP-TEE / optee_examples.git / 20e5a612e6303820c1e41faf8aa265404b28de82
commit20e5a612e6303820c1e41faf8aa265404b28de82[log] [tgz]
authorJerome Forissier <jerome.forissier@linaro.org>Thu Nov 22 17:26:32 2018 +0100
committerJérôme Forissier <jerome.forissier@linaro.org>Fri Nov 23 09:58:31 2018 +0100
treea2bb288cf4215b87d2e5cab9ac34cdddb97331f7
parent552c9d08acfaa13afe5699bbbc26f06b0cacb7ef [diff]
Remove misleading TA properties

Some of our example TAs define the following properties:
 - "gp.ta.description" (type: string)
 - "gp.ta.version" (type: unsigned 32-bit integer)

This is misleading, because these are *not* the standard description and
version properties defined by the GP Internal Core API specification. The
standard ones are:
 - "gpd.ta.description" (type: string)
 - "gpd.ta.version" (type: string)
OP-TEE TAs should use the TA_DESCRIPTION and TA_VERSION macros to define
them.

This commit gets rid of the misleading properties. Instead, TA_DESCRIPTION
and TA_VERSION are set in the hello_world application. To still illustrate
the mechanism used to define non-standard properties, we add a couple of
values with names that follow the recommended reverse domain name
convention. Other TAs are left with no additional properties and default
version and description for simplicity.

Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org>
3 files changed
tree: a2bb288cf4215b87d2e5cab9ac34cdddb97331f7
  1. acipher/
  2. aes/
  3. docs/
  4. hello_world/
  5. hotp/
  6. random/
  7. secure_storage/
  8. .gitignore
  9. Android.mk
  10. CMakeLists.txt
  11. CMakeToolchain.txt
  12. LICENSE
  13. Makefile
  14. README.md
README.md

OP-TEE Sample Applications

Contents

  1. Introduction
  2. List of sample applications
  3. How to build a Trusted Application

1. Introduction

This document describes the sample applications that are included in the OP-TEE, that aim to showcase specific functionality and use case.

For sake of simplicity, all OP-TEE example test application are prefixed with optee_example_.

2. List of sample applications

Directory hello_world/:

  • A very simple Trusted Application to answer a hello command and incrementing an integer value.
  • Test application: optee_example_hello_world
  • Trusted application UUID: 8aaaf200-2450-11e4-abe2-0002a5d5c51b

Directory random/:

  • Generates a random UUID using capabilities of TEE API (TEE_GenerateRandom()).
  • Test application: optee_example_random
  • Trusted application UUID: b6c53aba-9669-4668-a7f2-205629d00f86

Directory aes/:

  • Runs an AES encryption and decryption from a TA using the GPD TEE Internal Core API. Non secure test application provides the key, initial vector and ciphered data.
  • Test application: optee_example_aes
  • Trusted application UUID: 5dbac793-f574-4871-8ad3-04331ec17f24

Directory secure_storage/:

  • A Trusted Application to read/write raw data into the OP-TEE secure storage using the GPD TEE Internal Core API.
  • Test application: optee_example_secure_storage
  • Trusted application UUID: f4e750bb-1437-4fbf-8785-8d3580c34994

Directory acipher/:

  • Generates an RSA key pair of specified size and encrypts a supplied string with it using the GPD TEE Internal Core API.
  • Test application: optee_example_acipher
  • Trusted application UUID: a734eed9-d6a1-4244-aa50-7c99719e7b7b

3. How to build a Trusted Application

TA basics documentation presents the basics for implementing and building an OP-TEE trusted application.

One can also refer to the examples provided: source files and make scripts.