-
Notifications
You must be signed in to change notification settings - Fork 0
fix: keep the module verification command parseable #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified this fix and it's correct.
Before this change, the
printf '...'inside the (already single-quoted)phone '...'argument closed the outer quote early. Locally in bash, that split the intended one-argument command into several word-split arguments; sincephone()only reads$1, the remote script that actually reached the device was truncated right at...then printf— an unterminatedif. On a real device shell that's a syntax error, sosu -cfails non-zero and the local|| die 'installed module files do not match the payload'fires. Worse, by the time the parser hits that error, the precedingtar -xf,chown -R 0:0, and the stale-filerm -f "$stale"pruning loop have already run — so the module tree gets partially mutated even though the size/count safety check (the veryifblock meant to catch unexpected leftover files) and the final cleanup/exit 0never execute.Switching the inner
printfto double quotes removes the only other literal'in the string, so the whole thing is now one well-formed single-quoted argument again — I scanned it and confirmed there's exactly one opening and one closing'.The new
/bin/dash -nparse-check intests/simple-installer.test.mjs(line 323) is well-targeted: it validates the exact stringphone()hands to the device shell, which is precisely what would have caught this regression.ubuntu-latest(used in.github/workflows/check.yml) always ships/bin/dash, so no portability concern there.Scope-wise this PR only touches these two files — no DEVICE.json/build-target, kernel config, Wi-Fi policy, Docker startup, or packaging changes, and nothing that looks like firmware/credentials/generated-artifact inclusion. No further issues found.