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

Private Merkle Treaps shouldn't leak information through hashes #1

Open
Nuhvi opened this issue Mar 31, 2024 · 0 comments
Open

Private Merkle Treaps shouldn't leak information through hashes #1

Nuhvi opened this issue Mar 31, 2024 · 0 comments
Assignees
Labels
e2ee End to end encrypted data in the homeserver (including keys)

Comments

@Nuhvi
Copy link
Collaborator

Nuhvi commented Mar 31, 2024

For the eventual work on e2e encrypted (private) repos, hashes like the rank (hash of the key) or hashes of the node might leak some private information, for example there would be a globally well-known rank for the key bitcoin wallet backup, to avoid this, we should mix the encryption key (or a hash of it) with all hashing operations, so instead of rank = hash(key) it should be rank = hash(key | encrypitonKey) or rank = hash(key | hash(encryptionKey))

@Nuhvi Nuhvi self-assigned this Mar 31, 2024
@Nuhvi Nuhvi added the e2ee End to end encrypted data in the homeserver (including keys) label Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2ee End to end encrypted data in the homeserver (including keys)
Projects
None yet
Development

No branches or pull requests

1 participant