-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add secure element support #364
Comments
Is there any preview of the modified API ? |
I am curious about different chips support: and modules: and LoRaWAN Network Servers: |
I doubt that any of those secure elements will be supportable without NDA. However it would be helpful to get an idea where the interface internally is headed towards. For one to avoid duplicate work, and then to share some thoughts ... |
The secure element support is currently under development and should be made available once the 4.4.1 release is performed. Our current API specification can be found on the project's wiki Secure element API As mentioned by @GrumpyOldPizza most of the time the secure-elements support is done under NDA. Thus, our approach is to provide the building blocks to the secure-elements manufacturers to adapt their API to the one that we defined. For users that don't have access to a real secure-element we will provide a full software emulated secure-element. |
- Added a LoRaWAN layer frame counter handler - Added a LoRaWAN layer message parser - Added a LoRaWAN layer message serializer - Added a LoRaWAN layer header type definitions - Added a LoRaWAN layer message type definitions - Added a LoRaWAN layer internal types definition. Must not be include in application sources. #364
We will add the support for a secure element for the LoRaMac stack. The update comes with API changes for the cryptographic functions.
After the update, users can decide if they want to use cryptographics in software or in hardware (with a secure element).
The text was updated successfully, but these errors were encountered: