platform: integration of ATECC608 secure element #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joelguittet
force-pushed
the
feature/integration-secure-element
branch
2 times, most recently
from
b4a00ee to
9be680c
Compare
joelguittet
force-pushed
the
feature/integration-secure-element
branch
from
a23daf5 to
1d77e08
Compare
|
Kudos, SonarCloud Quality Gate passed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The purpose of this Pull Request is to integrate ATECC608 secure element to perform authentication of the device with the mender server. This will permit to avoid generating keys in the device and expose the private key (it will instead remains secret inside the secure element).
To achieve this integration, the platform directory architecture needs to be reworked to permit several implementation of each feature. At the same time weak implementation is added to permit user custom variant.
Particularly regarding the platform "tls" module, variants available at the end will be "mbedtls" (the current one and will remains the default), "cryptoauthlib" (library from microchip to interface secure element such as the ATECC608) and "weak" (that the developer can select to create it's own version of the variant).