Provisioning in Zephyr
summary
Zephyr-based provisioning here is concrete: a Rust CLI uses rcgen crate and serialport crate to pull a hardware ID, generate CA/server/client certs, and push them over AT commands into the nRF9160 modem keystore. Code calls Zephyr’s shell, settings API and tls_credential_add to register tags; EC certs sometimes fail because servers expect RSA. Storage choices are explicit: use the secure key store or external secure element, avoid filesystem cleartext, and gate boot on presence of certs and device ID.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:20PROVISIONING DEVICES
- 2:19GENERATING CERTIFICATES
- 11:16STORING CERTIFICATES
- 21:21DEVICE CONFIGURATION
related talks
22mSecure and Massive IoT Device Factory Provisioning
34mX.509 Client Authentication in Zephyr
16mDesigning Secure Systems for CRA Compliance leveraging Zephyr
40mZephyr Project Security Status
27mZephyr and Trusted Execution Environments
36mConnecting Zephyr Devices at Scale Using Open Source Solutions
27mZephyr and Trusted Execution Environments
10mLightning Talk: Open Source Fleet Management in Zephyr