RFC 0012: JIT account-access permission for ProductAccountId methods#136
Closed
filvecchiato wants to merge 2 commits into
Closed
RFC 0012: JIT account-access permission for ProductAccountId methods#136filvecchiato wants to merge 2 commits into
filvecchiato wants to merge 2 commits into
Conversation
…ethods Introduces a per-account just-in-time permission check for all Host API methods that accept a ProductAccountId, preventing cross-product identity leakage. Closes #134.
filvecchiato
force-pushed
the
rfc/0012-account-access-permission
branch
from
de59c08 to
935239c
Compare
filvecchiato
force-pushed
the
rfc/0012-account-access-permission
branch
from
935239c to
8bf1960
Compare
3 tasks
Contributor
Author
|
close in favour of paritytech/truapi#15 |
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.
RFC: JIT Account-Access Permission for ProductAccountId Methods
Summary
Introduces a per-account just-in-time (JIT) permission check for all Host API methods that accept a
ProductAccountId, preventing cross-product identity leakage. A malicious product can currently call account methods with another product'sDotNsIdentifierto obtain public keys, aliases, and proofs without user consent.Checklist
docs/rfcs/0012-account-access-permission.mdwith completed frontmatterdocs/rfcs/_index.mdwith a link to the new RFCrfc,proposalMotivation
Account methods (
host_account_get,host_account_get_alias,host_account_create_proof, signing methods,host_create_transaction,remote_statement_store_create_proof,host_payment_top_up) accept a caller-suppliedProductAccountIdbut have no permission gating. This allows cross-product user tracking and identity correlation without user awareness. See #134 for the full attack scenario.