Change Details

Develop a cc_3xx driver entry point for the aead multipart capability (aead_encrypt_multipart, aead_decrypt_multipart) List of entry points to be finalised first (done in the ticket) Modify the build system to build any additional source added. Make sure no tests break. Test enablement in the TF-M Crypto regression test suite: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11880 Associated mbedTLS work items (adding support only for GCM and ChaChaPoly at first): This is pending on this PR from mbedTLS for support on the backend side: https://github.com/ARMmbed/mbedtls/pull/4338 Associated ticket: https://github.com/ARMmbed/mbedtls/issues/3257 CCM support ticket is here: https://github.com/ARMmbed/mbedtls/issues/3721 with associated patch: https://github.com/ARMmbed/mbedtls/pull/5047 This would require some reworking of the low level CC driver as well as the current implementation only supports single-shot AEAD operations.

Develop a cc_3xx driver entry point for the aead multipart capability (aead_encrypt_multipart, aead_decrypt_multipart) List of entry points to be finalised first (done in the ticket) Modify the build system to build any additional source added. Make sure no tests break. Test enablement in the TF-M Crypto regression test suite: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11880 Support for AEAD multipart in TF-M frontend: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11825 (needs to be aligned with a new enough version of mbedTLS, i.e. TF-M will pick it up only with mbedTLS 3.1) Associated mbedTLS work items (adding support only for GCM and ChaChaPoly at first): This is pending on this PR from mbedTLS for support on the backend side: https://github.com/ARMmbed/mbedtls/pull/4338 Associated ticket: https://github.com/ARMmbed/mbedtls/issues/3257 CCM support ticket is here: https://github.com/ARMmbed/mbedtls/issues/3721 with associated patch: https://github.com/ARMmbed/mbedtls/pull/5047 This would require some reworking of the low level CC driver as well as the current implementation only supports single-shot AEAD operations.

Develop a cc_3xx driver entry point for the aead multipart capability (aead_encrypt_multipart, aead_decrypt_multipart) List of entry points to be finalised first (done in the ticket) Modify the build system to build any additional source added. Make sure no tests break. Test enablement in the TF-M Crypto regression test suite: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11880 Support for AEAD multipart in TF-M frontend: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11825 (needs to be aligned with a new enough version of mbedTLS, i.e. TF-M will pick it up only with mbedTLS 3.1) Associated mbedTLS work items (adding support only for GCM and ChaChaPoly at first): This is pending on this PR from mbedTLS for support on the backend side: https://github.com/ARMmbed/mbedtls/pull/4338 Associated ticket: https://github.com/ARMmbed/mbedtls/issues/3257 CCM support ticket is here: https://github.com/ARMmbed/mbedtls/issues/3721 with associated patch: https://github.com/ARMmbed/mbedtls/pull/5047 This would require some reworking of the low level CC driver as well as the current implementation only supports single-shot AEAD operations.