Skip to content
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

Potential Privacy leakage in the "move" function in example_cc.go #290

Open
ghost opened this issue May 19, 2024 · 0 comments
Open

Potential Privacy leakage in the "move" function in example_cc.go #290

ghost opened this issue May 19, 2024 · 0 comments

Comments

@ghost
Copy link

ghost commented May 19, 2024

The "move" fuunction in test/fixtures/testdata/go/src/github.com/example_cc/example_cc.go returns "transientData" in line 240, which is obtained from "GetTransient" in line 238. Since transient data is local to the peer and is private to other peers, there are two issues about this design:

  1. if transientData is private, the functions that query private data should be read-only, but "move" updates the world state.
  2. the transient data is local to the peer and will be exculded to the transaction, so how can other peers verify the "transientData"?
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

No branches or pull requests

0 participants