u-boot.git/include/fsl_validate.h, branch u-boot-2016.09.y

powerpc/mpc85xx: SECURE BOOT- Enable chain of trust in SPL

2016-07-21T18:09:23+00:00

As part of Chain of Trust for Secure boot, the SPL U-Boot will validate
the next level U-boot image. Add a new function spl_validate_uboot to
perform the validation.

Enable hardware crypto operations in SPL using SEC block.
In case of Secure Boot, PAMU is not bypassed. For allowing SEC block
access to CPC configured as SRAM, configure PAMU.

Reviewed-by: Ruchika Gupta 
Signed-off-by: Aneesh Bansal 
Signed-off-by: Sumit Garg 
Reviewed-by: Simon Glass 
Reviewed-by: York Sun

SECURE BOOT: Change fsl_secboot_validate func to pass image addr

2016-03-29T15:46:23+00:00

Use a pointer to pass image address to fsl_secboot_validate(),
instead of using environmental variable "img_addr".

Signed-off-by: Aneesh Bansal 
Signed-off-by: Saksham Jain 
Reviewed-by: York Sun

SECURE BOOT: Halt execution when secure boot fail

2016-03-29T15:46:23+00:00

In case of fatal failure during secure boot execution (e.g. header
not found), reset is asserted to stop execution. If the RESET_REQ
is not tied to HRESET, this allows the execution to continue.

Add esbh_halt() after the reset to make sure execution stops.

Signed-off-by: Aneesh Bansal 
Signed-off-by: Saksham Jain 
Reviewed-by: York Sun

armv8: fsl-lsch3: Add new header for secure boot

2016-03-29T15:46:20+00:00

For secure boot, a header is used to identify key table, signature
and image address. A new header structure is added for lsch3.

Currently key extension (IE) feature is not supported. Single key
feature is not supported. Keys must be in table format. Hence, SRK
(key table) must be present. Max key number has increase from 4 to
8. The 8th key is irrevocable. A new barker Code is used.

Signed-off-by: Aneesh Bansal 
Signed-off-by: Saksham Jain 
Reviewed-by: York Sun

secure_boot: enable chain of trust for ARM platforms

2016-01-27T16:12:49+00:00

Chain of Trust is enabled for ARM platforms (LS1021 and LS1043).
In board_late_init(), fsl_setenv_chain_of_trust() is called which
will perform the following:
- If boot mode is non-secure, return (No Change)
- If boot mode is secure, set the following environmet variables:
   bootdelay = 0 (To disable Boot Prompt)
   bootcmd = CONFIG_CHAIN_BOOT_CMD (Validate and execute Boot script)

Signed-off-by: Aneesh Bansal 
Acked-by: Ruchika Gupta 
Reviewed-by: York Sun

SECURE BOOT: support for validation of dynamic image

2016-01-25T16:24:16+00:00

Some images to be validated are relocated to a dynamic
address at run time. So, these addresses cannot be known
befor hand while signing the images and creating the header
offline.
So, support is required to pass the image address to the
validate function as an argument.
If an address is provided to the function, the address
field in Header is not read and is treated as a reserved
field.

Signed-off-by: Saksham Jain 
Signed-off-by: Aneesh Bansal 
Acked-by: Ruchika Gupta 
Reviewed-by: York Sun

SECURE BOOT: change prototype of fsl_secboot_validate function

2016-01-25T16:24:16+00:00

The prototype and defination of function fsl_secboot_validate
has been changed to support calling this function from another
function within u-boot.
Only two aruments needed:
1) header address - Mandatory
2) SHA256 string - optional

Signed-off-by: Saksham Jain 
Signed-off-by: Aneesh Bansal 
Acked-by: Ruchika Gupta 
Reviewed-by: York Sun

armv8/ls1043ardb: add SECURE BOOT target for NOR

2015-12-15T00:57:35+00:00

LS1043ARDB Secure Boot Target from NOR has been added.
- Configs defined to enable esbc_validate.
- ESBC Address in header is made 64 bit.
- SMMU is re-configured in Bypass mode.

Signed-off-by: Aneesh Bansal 
Reviewed-by: York Sun

Pointers in ESBC header made 32 bit

2015-10-29T17:33:57+00:00

For the Chain of Trust, the esbc_validate command supports
32 bit fields for location of the image. In the header structure
definition, these were declared as pointers which made them
64 bit on a 64 bit core.

Signed-off-by: Aneesh Bansal 
Reviewed-by: York Sun

SECURE BOOT: Add command for validation of images

2015-03-05T20:04:59+00:00

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]
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.

Signed-off-by: Ruchika Gupta 
Signed-off-by: Gaurav Rana 
Reviewed-by: York Sun