Repository navigation
Security Boundaries
Zachary Nathan Goode edited this page Oct 4, 2026
·
1 revision
This prototype has security-relevant limitations that must remain visible in published documentation.
- Plain HTTP: device control and password traffic are not shown as encrypted in transit.
- Open provisioning: the setup access point has no password.
-
Password scope: passwords are stored as strings in firmware NVS and compared with
strcmp(). Password checks appear in password-management and factory-reset operations, not as global ordinary-API authorization. -
Windows persistence: remembered passwords are plain JSON under
%AppData%\FileLinkDiscovery\device_passwords.json. - OTA: normal ESP-IDF image validation is used, but signed-image policy, secure boot, transport encryption, custom anti-rollback, and OTA authorization are not established.
- SD paths: runtime path validation exists, but the 127-character logical path limit is not uniformly enforced by all API entry points.
These facts describe implementation boundaries. They are not a security assessment or a suitability statement for an untrusted network.