You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "PetervdPerk-NXP (via GitHub)" <gi...@apache.org> on 2023/08/22 09:20:32 UTC

[GitHub] [nuttx] PetervdPerk-NXP commented on pull request #10249: Added NXP SE05x support (secure element)

PetervdPerk-NXP commented on PR #10249:
URL: https://github.com/apache/nuttx/pull/10249#issuecomment-1687805438

   We try to write a dedicated code for NuttX whenever possible i.e. S32K1, S32K3, IMXRT and SocketCAN.
   For the SE050 secure element we took a different approach because of complexity of the Application Protocol Data Unit (APDU) and maintaining the security updates through the external repository. The [repository ](https://github.com/NXPPlugNTrust/nano-package)we use is open-source and Apache 2.0 licensed.
   
   > make it impossible to reuse code in similar crypto drivers.
   
   We took an approach to abstract the Secure Element through the introduced ` _SEIOCBASE` ioctl. With generic commands such as `SEIOC_GENERATE_KEYPAIR` any other crypto/secure element driver can reuse this interface.
   
   Also how come it's okay for a wireless driver i.e. ESP32, ESP32C3, BL602, NRF52, NRF53 and NRF91 to pull from external repositories and now for a secure element it's not?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org