Skip to content

feat: RemoteTriggerRule.rejectUnsignedCommands opt-in - #91

Merged
vietnguyentuan2019 merged 1 commit into
mainfrom
feat/reject-unsigned-remote-commands
Nov 7, 2026
Merged

vietnguyentuan2019 merged 1 commit into
mainfrom
feat/reject-unsigned-remote-commands

Conversation

@vietnguyentuan2019

Copy link
Copy Markdown
Contributor

Follow-up from the v2 signature work. Adds an opt-in to refuse native_wm direct commands on a rule that has no secretKey. Default is false, so nothing changes unless you set it.

  • flag lives in SharedPreferences / UserDefaults (it is not a secret), so no DB migration on either platform
  • decision logic is one small function in Kotlin and Swift, unit tested (Kotlin 11 / Swift 9 pass), plus a Dart test that both bridges read the same key (toMap tests alone wouldnt catch a dropped key)
  • iOS still runs native_wm when no rule is registered at all, Android ignores it. Not changed here, documented in doc/REMOTE_TRIGGER_SIGNING.md

Not tested end to end with a real push.

Opt-in refusal of native_wm direct commands on a rule without a secretKey. Default
unchanged (accepted + warning). Flag stored in SharedPreferences/UserDefaults (no DB
migration), decision logic shared + unit-tested in Kotlin and Swift, key-name parity test.
@vietnguyentuan2019
vietnguyentuan2019 merged commit c34a52c into main Nov 7, 2026
13 checks passed
@vietnguyentuan2019
vietnguyentuan2019 deleted the feat/reject-unsigned-remote-commands branch November 7, 2026 09:26
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