[people/ms/u-boot.git] / doc / README.esbc_validate

/*
 * (C) Copyright 2015
 *
 * SPDX-License-Identifier:	GPL-2.0+
 */

esbc_validate command
========================================

1. esbc_validate command is meant for validating header and
    signature of images (Boot Script and ESBC uboot client).
    SHA-256 and RSA operations are performed using SEC block in HW.
    This command works on both PBL based and Non PBL based Freescale
    platforms.
   Command usage:
    esbc_validate img_hdr_addr [pub_key_hash]
    esbc_validate hdr_addr <hash_val>
     Validates signature using RSA verification.
     $hdr_addr Address of header of the image to be validated.
     $hash_val -Optional. It provides Hash of public/srk key to be
       used to verify signature.

2. ESBC uboot client can be linux. Additionally, rootfs and device
    tree blob can also be signed.
3. In the event of header or signature failure in validation,
    ITS and ITF bits determine further course of action.
4. In case of soft failure, appropriate error is dumped on console.
5. In case of hard failure, SoC is issued RESET REQUEST after
    dumping error on the console.
6. KEY REVOCATION Feature:
    QorIQ platforms like B4/T4 have support of srk key table and key
    revocation in ISBC code in Silicon.
    The srk key table allows the user to have a key table with multiple
    keys and revoke any key in case of particular key gets compromised.
    In case the ISBC code uses the key revocation and srk key table to
    verify the u-boot code, the subsequent chain of trust should also
    use the same.
6. ISBC KEY EXTENSION Feature:
    This feature allows large number of keys to be used for esbc validation
    of images. A set of public keys is being signed and validated by ISBC
    which can be further used for esbc validation of images.
Commit	Line	Data
47151e4b	1	/*
	2	* (C) Copyright 2015
	3	*
	4	* SPDX-License-Identifier: GPL-2.0+
	5	*/
	6
	7	esbc_validate command
	8	========================================
	9
	10	1. esbc_validate command is meant for validating header and
	11	signature of images (Boot Script and ESBC uboot client).
	12	SHA-256 and RSA operations are performed using SEC block in HW.
	13	This command works on both PBL based and Non PBL based Freescale
	14	platforms.
	15	Command usage:
	16	esbc_validate img_hdr_addr [pub_key_hash]
	17	esbc_validate hdr_addr <hash_val>
	18	Validates signature using RSA verification.
	19	$hdr_addr Address of header of the image to be validated.
	20	$hash_val -Optional. It provides Hash of public/srk key to be
	21	used to verify signature.
	22
	23	2. ESBC uboot client can be linux. Additionally, rootfs and device
	24	tree blob can also be signed.
	25	3. In the event of header or signature failure in validation,
	26	ITS and ITF bits determine further course of action.
	27	4. In case of soft failure, appropriate error is dumped on console.
	28	5. In case of hard failure, SoC is issued RESET REQUEST after
	29	dumping error on the console.
	30	6. KEY REVOCATION Feature:
	31	QorIQ platforms like B4/T4 have support of srk key table and key
	32	revocation in ISBC code in Silicon.
	33	The srk key table allows the user to have a key table with multiple
	34	keys and revoke any key in case of particular key gets compromised.
	35	In case the ISBC code uses the key revocation and srk key table to
	36	verify the u-boot code, the subsequent chain of trust should also
	37	use the same.
	38	6. ISBC KEY EXTENSION Feature:
	39	This feature allows large number of keys to be used for esbc validation
	40	of images. A set of public keys is being signed and validated by ISBC
	41	which can be further used for esbc validation of images.