Add lockdown disable + DISABLED status for runtime lockdown toggle#927
Closed
niccellular wants to merge 2 commits into
Closed
Add lockdown disable + DISABLED status for runtime lockdown toggle#927niccellular wants to merge 2 commits into
niccellular wants to merge 2 commits into
Conversation
Supports moving MESHTASTIC_LOCKDOWN from a compile-time build flag to a runtime, client-toggleable setting. - AdminMessage.LockdownAuth.disable (field 6): with a valid passphrase, reverts the device out of lockdown — decrypt all stored config back to plaintext, drop the wrapped DEK / unlock token / monotonic counter / backoff files, reboot into normal mode. APPROTECT is explicitly NOT reversed (the debug-port lockout is permanent on silicon where it is effective; only a full chip erase clears it). - FromRadio.LockdownStatus.State.DISABLED (value 5): reported by a lockdown-capable device that is not currently in lockdown, so a client can render its 'lockdown mode' toggle as OFF. Distinct from NEEDS_PROVISION, which is only used mid-enable.
This was referenced May 29, 2026
thebentern
approved these changes
Jun 2, 2026
Member
Author
|
@copilot resolve the merge conflicts in this pull request |
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the two wire-format pieces needed to move
MESHTASTIC_LOCKDOWNfrom a compile-time build flag to a runtime, client-toggleable setting (Android/iOS "lockdown mode" switch).AdminMessage.LockdownAuth.disable(field 6) — with a valid passphrase in the same message, reverts a device out of lockdown: the firmware decrypts every stored config/channel/nodedb file back to plaintext, removes the wrapped DEK / unlock token / monotonic-counter / backoff files, and reboots into normal mode. The inverse of the existing provision/unlock path.FromRadio.LockdownStatus.State.DISABLED(value 5) — reported by a lockdown-capable device that isn't currently in lockdown, so a client can render its toggle as OFF. Distinct fromNEEDS_PROVISION(used only mid-enable).Notes
disablerequires the passphrase — the device must prove operator ownership before reverting at-rest encryption.boots_remaining/valid_until_epoch/max_session_seconds/lock_noware ignored whendisable=true.protoc.Test plan
buf lint/buf breakingpass in CI