166363f2ed
This Trusted Application allows enabling SCP03 as well as provisioning the keys on TEE controlled secure element (ie, NXP SE050). All the information flowing on buses (ie I2C) between the processor and the secure element must be encrypted. Secure elements are pre-provisioned with a set of keys known to the user so that the secure channel protocol (encryption) can be enforced on the first boot. This situation is however unsafe since the keys are publically available. For example, in the case of the NXP SE050, these keys would be available in the OP-TEE source tree [2] and of course in the documentation corresponding to the part. To address that, users are required to rotate/provision those keys (ie, generate new keys and write them in the secure element's persistent memory). For information on SCP03, check the Global Platform HomePage and google for that term [1] [1] globalplatform.org [2] https://github.com/OP-TEE/optee_os/ check: core/drivers/crypto/se050/adaptors/utils/scp_config.c Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io> Reviewed-by: Simon Glass <sjg@chromium.org>
22 lines
538 B
C
22 lines
538 B
C
/* SPDX-License-Identifier: BSD-3-Clause */
|
|
/*
|
|
* (C) Copyright 2021, Foundries.IO
|
|
*
|
|
*/
|
|
#ifndef __TA_SCP03_H
|
|
#define __TA_SCP03_H
|
|
|
|
#define PTA_SCP03_UUID { 0xbe0e5821, 0xe718, 0x4f77, \
|
|
{ 0xab, 0x3e, 0x8e, 0x6c, 0x73, 0xa9, 0xc7, 0x35 } }
|
|
|
|
/*
|
|
* Enable Secure Channel Protocol functionality (SCP03) on the Secure Element.
|
|
* Setting the operation value to something different than NULL will trigger
|
|
* the SCP03 provisioning request.
|
|
*
|
|
* in params[0].a = operation
|
|
*/
|
|
#define PTA_CMD_ENABLE_SCP03 0
|
|
|
|
#endif /*__TA_SCP03_H*/
|