Repository navigation
Replies: 2 comments 11 replies
|
Okay, I only have some official pico2 as spare keys. Are they sufficient for the testing requirements? |
7 replies
|
It is a good idea, but the importance here is not to over-advertise this as a security improvements. It shrinks the attack surface a bit, but it is still not a secure element as such. P.S. out of context, but related: have you researching attaching a separate SE element via I2C? |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
@token2 @lockedmutex @cresseelia @netll @mannp @Curious-r @ncmro7 @lpiob @JDestiny @Babel36acl
Hi everyone. For the past two months, I’ve been working on a major update: the firmware now supports a Secure/Non-Secure split via TrustZone, which is enabled by default. Before I push a new release, I’d like you to test this version if you have the capacity to do so. It’s available in the
developbranch, and both the documentation and the build process have been updated accordingly. I recommend testing it first on boards that do not contain any of your production secrets. Ideally, you should test all the applets you use, but please do so using test or backup data—data that you can afford to lose or otherwise recover.I anticipate the testing phase will last for two weeks (until November 21, 2026). Afterward, I will address any remaining issues or bugs and prepare the final 0.5.0 release. If you encounter any problems, feel free to post in this thread or open a separate issue—whichever you prefer; either way is fine. Thanks for your time and attention.
Target branch: https://github.com/TheMaxMur/RS-Key/tree/develop
Docs:
https://themaxmur.github.io/RS-Key/develop/build.html
https://themaxmur.github.io/RS-Key/develop/architecture.html
https://themaxmur.github.io/RS-Key/develop/production.html
All reactions