feat(build): put crttool in the build directorySame as fiptool. Move all artefacts to the platform build directory andconvert to the standard build macro to make things more generic. Leavea symli
feat(build): put crttool in the build directorySame as fiptool. Move all artefacts to the platform build directory andconvert to the standard build macro to make things more generic. Leavea symlink for the final binary in case someone depends on it.Change-Id: I82ef846a95474ba385377032fb185e548827bf5cSigned-off-by: Boyan Karatotev <boyan.karatotev@arm.com>
show more ...
fix(tools): update the fiptool and certtool to fix POSIX buildThis patch fixes below issue raised:https://github.com/TrustedFirmware-A/trusted-firmware-a/issues/8https://github.com/TrustedFirmwa
fix(tools): update the fiptool and certtool to fix POSIX buildThis patch fixes below issue raised:https://github.com/TrustedFirmware-A/trusted-firmware-a/issues/8https://github.com/TrustedFirmware-A/trusted-firmware-a/issues/9https://github.com/TrustedFirmware-A/trusted-firmware-a/issues/10Change-Id: I521bf7410535ffe49198789ba183cc401b3b88a0Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
feat(cert-create): add pkcs11 engine supportAdd pkcs11 engine support which allows using keys that are securelystored on a HSM or TPM. To use this feature the user has to supplyan RFC 7512 compli
feat(cert-create): add pkcs11 engine supportAdd pkcs11 engine support which allows using keys that are securelystored on a HSM or TPM. To use this feature the user has to supplyan RFC 7512 compliant PKCS11 URI to a key instead of a file as anargument to one of the key options. This change is fully backwardscompatible.This change makes use of the openssl engine API which is deprecatedsince openssl 3.0 and will most likely be removed in version 4. Sopkcs11 support will have to be updated to the openssl provider APIin the near future.Signed-off-by: Robin van der Gracht <robin@protonic.nl>Change-Id: If96725988ca62c5613ec59123943bf15922f5d1f
cert_create: add Platform owned secure partitions supportAdd support to generate a certificate named "plat-sp-cert" for SecurePartitions(SP) owned by Platform.Earlier a single certificate file "s
cert_create: add Platform owned secure partitions supportAdd support to generate a certificate named "plat-sp-cert" for SecurePartitions(SP) owned by Platform.Earlier a single certificate file "sip-sp-cert" was generated whichcontained hash of all 8 SPs, with this change SPs are divided intotwo categories viz "SiP owned" and "Plat owned" containing 4 SPs each.Platform RoT key pair is used for signing.Signed-off-by: Manish Pandey <manish.pandey2@arm.com>Change-Id: I5bd493cfce4cf3fc14b87c8ed1045f633d0c92b6
cert_tool: Update cert_tool for fw_config image supportUpdated cert_tool to add hash information of fw_config image intothe existing "trusted boot fw" certificate.Signed-off-by: Manish V Badarkh
cert_tool: Update cert_tool for fw_config image supportUpdated cert_tool to add hash information of fw_config image intothe existing "trusted boot fw" certificate.Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>Change-Id: I720319225925806a2a9f50a1ac9c8a464be975f0
cert_create: add SiP owned secure partitions supportAdd support to generate certificate "sip-sp-cert" for SecurePartitions(SP) owned by Silicon provider(SiP).To avoid deviation from TBBR specific
cert_create: add SiP owned secure partitions supportAdd support to generate certificate "sip-sp-cert" for SecurePartitions(SP) owned by Silicon provider(SiP).To avoid deviation from TBBR specification the support is only added fordualroot CoT and not for TBBR CoT.A single certificate file is generated containing hash of individualpackages. Maximum 8 secure partitions are supported.Following new options added to cert_tool: --sip-sp-cert --> SiP owned Secure Partition Content Certificate --sp-pkg1 --> Secure Partition Package1 file --sp-pkg2 ..... --sp-pkg8Trusted world key pair is used for signing.Going forward, this feature can be extended for Platfrom ownedPartitions, if required.Signed-off-by: Manish Pandey <manish.pandey2@arm.com>Change-Id: Ia6dfbc1447cfb41b1fcbd12cf2bf7b88f409bd8d
cert_create: Define the dualroot CoTSelection of the chain of trust is done through the COT build option:> make COT=dualrootChange-Id: Id87c7a5116bdd13bdb29645ecf31d111ad094c1eSigned-off-by: S
cert_create: Define the dualroot CoTSelection of the chain of trust is done through the COT build option:> make COT=dualrootChange-Id: Id87c7a5116bdd13bdb29645ecf31d111ad094c1eSigned-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>