Skip to content

Releases: nrfconnect/sdk-trusted-firmware-m

ncs-v3.0.99-snapshot1: [nrf noup] partitions: crypto: Fix duplicate functions

30 May 12:38

Choose a tag to compare

The Oberon PSA core provides these two functions:
psa_key_derivation_verify_key
psa_key_derivation_verify_bytes

TF-M is not aware of the Oberon PSA core and it seems
that the core that they use doesn't provide these functions
at all. So instead of the usual logic of prefixing the PSA
core functions with the mbedcrypto__ prefix it skipped these.
We cannot skip the prefixing because the Oberon PSA core
implements these and thus we will get multiple definitions
errors.

Ref: NCSDK-33148

Signed-off-by: Georgios Vasilakis <[email protected]>

v2.1.1-ncs4-snapshot1: [nrf noup] crypto: Have CRYPTO_HW_ACCELERATOR support nrf_security

23 Apr 13:48

Choose a tag to compare

Adjust CRYPTO_HW_ACCELERATOR build scripts to also support
nrf_security.

Signed-off-by: Sebastian Bøe <[email protected]>
Signed-off-by: Joakim Andersson <[email protected]>
(cherry picked from commit c136210082623a0643700832292356fa5a2bb2ae)
(cherry picked from commit 38341177b624dd6655e73aa3991085b9825292ed)
Signed-off-by: Joakim Andersson <[email protected]>
(cherry picked from commit 2bdad64794b9c61fe85c7b5ad11c017a02ba9056)
Signed-off-by: Markus Swarowsky <[email protected]>
Change-Id: Ied8e378ef55fe398ea4e45f65b3c270e9e9cd030
Signed-off-by: Markus Swarowsky <[email protected]>
(cherry picked from commit 5903966d16a4f1d5eb338cf9f03e278d43481124)
Signed-off-by: Markus Swarowsky <[email protected]>
(cherry picked from commit a3a03e56f9a9816d93a6810d6f049b4f0759e45a)
Signed-off-by: Frank Audun Kvamtrø <[email protected]>
(cherry picked from commit 3f08f2595d976624e42478bb377cb24798b00a5d)
Signed-off-by: Tomi Fontanilles <[email protected]>

v2.1.1-ncs5-snapshot: [nrf fromtree] Protected Storage: Do not align NV counters in init

10 Apr 12:30

Choose a tag to compare

NVC_2 and NVC_3 should not be aligned to NVC_1 unless the
object table has been successfully stored to persistent
memory.

When storing an object to PS, the object is stored first
and the object table is updated afterwards. If there is not
enough memory for the object table, NVC_1 is increased, but
NVC_2 and NVC_3 are not. Reset the device. Object table is
validated with NVC_3. Now, if NVC_2 and NVC_3 are brought
to be on par with NVC_1 and the object table is not saved
and the device is reset again, the object table can no
longer be validated. New object tables are created,
which loses all the data stored to PS.

Change-Id: I9eb680d507d5aac251bede586b6c39c751815dcb
Signed-off-by: Markus Lassila <[email protected]>
(cherry picked from commit c08e9ef89a35a546291af699f378ee9acc661fa7)

sdk-trusted-firmware-m v2.1.1-ncs2

18 Dec 11:42
v2.1.1-ncs2

Choose a tag to compare

sdk-trusted-firmware-m v2.1.1-ncs2

sdk-trusted-firmware-m v2.1.1-ncs1

14 Nov 12:18
v2.1.1-ncs1

Choose a tag to compare

sdk-trusted-firmware-m v2.1.1-ncs1

sdk-trusted-firmware-m v2.0.0-ncs2

04 Jul 12:53
v2.0.0-ncs2

Choose a tag to compare

sdk-trusted-firmware-m v2.0.0-ncs2

sdk-trusted-firmware-m v2.0.0-ncs1-1

25 Apr 11:49
v2.0.0-ncs1-1

Choose a tag to compare

sdk-trusted-firmware-m v2.0.0-ncs1-1

sdk-trusted-firmware-m v1.8.0-ncs1-3

25 Apr 11:49
v1.8.0-ncs1-3

Choose a tag to compare

sdk-trusted-firmware-m v1.8.0-ncs1-3

sdk-trusted-firmware-m v2.0.0-ncs1

13 Mar 14:45
v2.0.0-ncs1

Choose a tag to compare

sdk-trusted-firmware-m v2.0.0-ncs1

sdk-trusted-firmware-m v1.8.0-ncs1-1

18 Dec 20:09
v1.8.0-ncs1-1

Choose a tag to compare

sdk-trusted-firmware-m v1.8.0-ncs1-1