Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed: Update crypto API to use a Microship secure element such as ATECC608A #235

Closed
wants to merge 6 commits into from

Conversation

LizzieDE110
Copy link

I am working on boards that embed an ATECC608A (Microchip secure element), and I would like to perform all ECC/ECDH operations using it. This approach offers the benefit of enhanced security, as private keys are not directly manipulated.

Initially, I am working with RIOT. When I started looking for solutions to secure RF communication, I came across tinydtls and was convinced by its implementation of DTLS. I noticed some issues on my board (reported here Issue 224), and a PR to replace ecc with micro-ecc is now open (PR 229).

Micro-ecc works on my boards and significantly accelerates the handshake process. However, as mentioned earlier, I have an ATECC608A on my boards, so I would like to add a feature allowing users to choose whether to use it or not.

Since not all boards embed a secure element, I have added an environment variable (DTLS_ATECC608A) to give users the choice to use it or not. The CryptoAuth library is used to control the secure element (CryptoAuthLib).

This PR is still a work in progress, but I have opened it so that we can discuss and improve my work.

@LizzieDE110 LizzieDE110 closed this Mar 4, 2024
@LizzieDE110 LizzieDE110 reopened this Mar 4, 2024
@LizzieDE110 LizzieDE110 closed this Mar 4, 2024
@LizzieDE110 LizzieDE110 deleted the atecc608a branch March 4, 2024 13:39
@LizzieDE110 LizzieDE110 changed the title WIP: Update crypto API to use a Microship secure element such as ATECC608A Removed: Update crypto API to use a Microship secure element such as ATECC608A Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant