Skip to content

common_boot: add locally managed ID warning - #938

Merged
JordanYates merged 3 commits into
mainfrom
feature/security_clarification
Jul 22, 2026
Merged

common_boot: add locally managed ID warning#938
JordanYates merged 3 commits into
mainfrom
feature/security_clarification

Conversation

@JordanYates

Copy link
Copy Markdown
Contributor

Add a warning output on boot if a locally managed device ID is found, which notifies the user that Infuse-IoT cloud does not know about this device, and cannot be used to run authenticated commands like RPCs etc.

Includes minor API usage updates to the security module.

In `derive_shared_secret`, ensure that the attributes object always
starts with the correct default value, so there can never be a path
with uninitialised memory.

Signed-off-by: Jordan Yates <jordan@embeint.com>
When resetting keys, delete them through the `psa_destroy_key` API
instead of deleting through the underlying ITS API. This ends up in the
same place, but eliminates a mismatch in the APIs used to create and
destroy keys, and ensures any metadata at the PSA level is removed.

Signed-off-by: Jordan Yates <jordan@embeint.com>
Add a warning output on boot if a locally managed device ID is found,
which notifies the user that Infuse-IoT cloud does not know about this
device, and cannot be used to run authenticated commands like RPCs etc.

The only use for locally managed mode is to observe Bluetooth
advertising broadcasts while first trying out Infuse-IoT.

Signed-off-by: Jordan Yates <jordan@embeint.com>
@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Jul 22, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
lib/security/security.c 85.71% 0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

@JordanYates
JordanYates merged commit f95cd28 into main Jul 22, 2026
14 checks passed
@JordanYates
JordanYates deleted the feature/security_clarification branch July 22, 2026 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant