Searched hist:dfeed9241800a4263bc76ee3a2fb8edae2c1498a (Results 1 – 3 of 3) sorted by relevance
| /optee_os/core/include/drivers/ |
| H A D | zynqmp_huk.h | dfeed9241800a4263bc76ee3a2fb8edae2c1498a Sat May 07 05:49:12 UTC 2022 Vesa Jääskeläinen <vesa.jaaskelainen@vaisala.com> drivers: zynqmp_huk: Add AES eFuse and HUK seed support
When AES eFuse is used to encrypt boot loaders and bitstreams then PUF
functionality is not available for use. When AES eFuse based encryption is
in use AES eFuse key becomes device key instead of PUF generated key.
In order to re-plenish additional device specific entropy that PUF would
provide utilize selected set of User programmable eFuses.
Selected user eFuses should be programmed during device manufacturing with
cryptographically good random numbers.
Signed-off-by: Vesa Jääskeläinen <vesa.jaaskelainen@vaisala.com>
Acked-by: Etienne Carriere <etienne.carriere@linaro.org>
|
| /optee_os/core/drivers/ |
| H A D | zynqmp_huk.c | dfeed9241800a4263bc76ee3a2fb8edae2c1498a Sat May 07 05:49:12 UTC 2022 Vesa Jääskeläinen <vesa.jaaskelainen@vaisala.com> drivers: zynqmp_huk: Add AES eFuse and HUK seed support
When AES eFuse is used to encrypt boot loaders and bitstreams then PUF
functionality is not available for use. When AES eFuse based encryption is
in use AES eFuse key becomes device key instead of PUF generated key.
In order to re-plenish additional device specific entropy that PUF would
provide utilize selected set of User programmable eFuses.
Selected user eFuses should be programmed during device manufacturing with
cryptographically good random numbers.
Signed-off-by: Vesa Jääskeläinen <vesa.jaaskelainen@vaisala.com>
Acked-by: Etienne Carriere <etienne.carriere@linaro.org>
|
| /optee_os/core/arch/arm/plat-zynqmp/ |
| H A D | conf.mk | dfeed9241800a4263bc76ee3a2fb8edae2c1498a Sat May 07 05:49:12 UTC 2022 Vesa Jääskeläinen <vesa.jaaskelainen@vaisala.com> drivers: zynqmp_huk: Add AES eFuse and HUK seed support
When AES eFuse is used to encrypt boot loaders and bitstreams then PUF
functionality is not available for use. When AES eFuse based encryption is
in use AES eFuse key becomes device key instead of PUF generated key.
In order to re-plenish additional device specific entropy that PUF would
provide utilize selected set of User programmable eFuses.
Selected user eFuses should be programmed during device manufacturing with
cryptographically good random numbers.
Signed-off-by: Vesa Jääskeläinen <vesa.jaaskelainen@vaisala.com>
Acked-by: Etienne Carriere <etienne.carriere@linaro.org>
|