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

Try proving a stronger form of the dapol security definitions #168

Open
Stentonian opened this issue Jul 6, 2024 · 1 comment
Open

Try proving a stronger form of the dapol security definitions #168

Stentonian opened this issue Jul 6, 2024 · 1 comment
Labels
Effort: much Large piece of work security Important security task

Comments

@Stentonian
Copy link

Stentonian commented Jul 6, 2024

The dapol security & privacy definitions rely on the tree being privately held by the custodian. It may be useful to be able to share the whole tree with a 3rd party. So it would then be necessary to adjust the security definitions to allow for shareable trees, and try prove them for dapol.

dapol paper: https://eprint.iacr.org/2021/1350

It would be useful to have this property because a) the custodian can share the tree with an auditor/regulator, and b) a 3rd party that will facilitate the generation of Merkle inclusion proofs for users so that the custodian does not know which ones are verifying.

In the privacy definitions the adversary has access to some subset of the database $\text{DB}[V]$ where $V$ is a set of corrupted users. They also have access to the inclusion proofs of $V$. If the whole tree is to be made public then the adversary would gain access to the inclusion proofs of all users $U$.

@Stentonian Stentonian added Effort: much Large piece of work security Important security task labels Jul 6, 2024
@Stentonian
Copy link
Author

The one thing that the adversary could gain info-wise is tighter bounds on the number of users. We could adjust the way the tree is constructed to further obfuscate this data: https://hackmd.io/8HN5hgvXRfm2CVfeaMyhNA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Effort: much Large piece of work security Important security task
Projects
None yet
Development

No branches or pull requests

1 participant