Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Hardware Secure Element Support? ATECC608A/B Specifically?
See original GitHub issueConfirm by changing [ ] to [x] below:
- [X ] I’ve searched for previous similar issues and didn’t find any solution
Known Issue
- [X ] I’m using ATS data type endpoint: the endpoint should look like
<prefix>-ats.iot.<region>.amazonaws.com
Platform/OS/Hardware/Device What are you running the sdk on?
Linux, ARM64 (Pocketbeagle)
Describe the question
Is there a pattern or recommendation for using certificates stored in a hardware secure element such as the ATECC608A? AWS IoT Greengrass supports this element and is an AWS certified solution and it exposes a PCKS#11 interface and is well supported on Linux and storing private key materials on filesystems on Linux machines no matter how “secure” does not appeal or work for most applications.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Are you looking for something like pkcs#11 support? We have this queued in the backlog but it hasn’t made it to the top of the priorities list yet. If that’s what you’re looking for could you let us know so we can update the priority?
Alternatively the SDK has an api for doing this from in-memory. That doesn’t help with the most secure requirements where you can’t even load to memory, but if you can that would provide a work around for the time being.