Hi PSA Crypto Developer Forum Organizer,

 

I’m currently integrating PSA Crypto Drivers into our codebase for hardware that includes CryptoCell module.

While reviewing the Github repositories, I noticed that t-psa-crypto-drivers do not appear to publish tagged releases.

https://github.com/Mbed-TLS/tf-psa-crypto-drivers

 

In contrast, tf-psa-crypto provides official releases:

https://github.com/Mbed-TLS/TF-PSA-Crypto

 

I also noticed that tf-psa-crypto-drivers appears to have some dependencies on the TFM code (e.g. crypto_driver_random.h, tfm_utils.h,  cc3xx_aes_external_key_loader.c, etc…)

 

Is there any documentation that describes the dependency relationship and version mapping between TF-PSA-Crypto, TF-PSA-Crypto-Drivers commit, and TF-M?

 

For example, if we choose TF-PSA-Crypto 1.2.0, how can we determine which tf-psa-crypto-drivers and TFM commit point were used in the official testing and validation of TF-PSA-Crypto release?

 

Any guidance or pointers to the relevant release notes or documentation would be greatly appreciated.

Thank you.

 

Regards,

 

Masaki Sato



CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be Garmin confidential and/or Garmin legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.