SB-992: add auth_challenge/auth_response protocol messages#19
Merged
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
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
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
Resolves SB-992 (security finding A4) — shared protocol piece.
Adds the two wire-protocol messages for the connect-time key-possession handshake used by the agent and mobile app.
Changes
AuthChallengeEvent { type: 'auth_challenge', nonce: string }(host → mobile).AuthResponseRequest { type: 'auth_response', mac: string }(mobile → host).nonceandmacare base64 strings, bounded byMAX_AUTH_BLOB_LENGTH(128) and validated indecode.isRequestasymmetry: the security gate lives on the agent (GoIsRequestexcludesauth_response); the mobile never decodes or re-sends it.Test Plan
npm test— round-trip + validation tests pass (incl. new auth_challenge/auth_response cases).Cross-repo
Consumed by
pocketmux-mobile; mirrored manually inpmux-agent.