feat: derive product entropy from rootEntropySource (RFC-7)#205
Merged
Conversation
9ce96fe to
340c62d
Compare
Contributor
|
Will fix codecs and then LGTM |
…pySource (RFC-7) Wire the RFC-0007 `rootEntropySource` through the SSO handshake so a host can serve `host_derive_entropy` deterministically without holding the raw root account secret. - host-papp: append `rootEntropySource` ([u8; 32]) to the `HandshakeSuccessV2` body (258 bytes; null for older peers). This revision is not yet pinned in the Mobile SSO spec (latest defined is v0.2.2, kept as `HandshakeSuccessV2_v022`). Thread it through the success state and persist it in `userSecretRepository` as `Option(Bytes(32))`, exposed via `papp.secrets`. - host-container: add `deriveProductEntropyFromSource(rootEntropySource, productId, key)` (layers 2-3); `deriveProductEntropy` now delegates to it. Refs #204.
340c62d to
7e1b3d2
Compare
johnthecat
added a commit
that referenced
this pull request
Jun 12, 2026
Main (0.8.7) had independently absorbed nearly all of this branch's work via PRs #178/#202/#205/#206/#212/#215/#216, with newer/cleaner versions. Conflict resolution (38 files): - package.json (x14), package-lock.json, CHANGELOG.md, migration doc: took main (newer versions, canonical release history). Dropped the unused `verifiablejs` dep. - All SSO V2, statement-store, handoff-service, and host-chat *impl* files: took main — strictly newer (ECDH session-key derivation #206, RFC-7 entropy #205, statement-store fix #215). The branch's parallel May implementations are superseded. - watchIdentity series: already identical in main (no real conflict). - Kept BRANCH version for two files where it is genuinely ahead: * identity/rpcAdapter.ts — defensive snake_case/camelCase Resources decode (fixes "Unknown user" regression on V2 runtime); a clean superset of main's version. * host-chat/codec/attachment.spec.ts — extra blurhash-thumbnail and NodeEndpoint round-trip tests against a byte-identical codec impl. Verified: build, typecheck, lint (0 errors), 679/679 tests pass.
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.
Wire the RFC-0007
rootEntropySourcethrough the SSO handshake so a host can servehost_derive_entropydeterministically without holding the raw root account secret.rootEntropySource([u8; 32]) to theHandshakeSuccessV2body (258 bytes;nullfor older peers). This revision is not yet pinned in the Mobile SSO spec (latest defined is v0.2.2, kept asHandshakeSuccessV2_v022). Thread it through the success state and persist it inuserSecretRepositoryasOption(Bytes(32)), exposed viapapp.secrets.deriveProductEntropyFromSource(rootEntropySource, productId, key)(RFC-7 layers 2–3);deriveProductEntropynow delegates to it.Closes #204.