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

Bruteforce ballot re-encryption allows ballot de-anonimization #22

Open
emduc opened this issue Dec 1, 2021 · 0 comments
Open

Bruteforce ballot re-encryption allows ballot de-anonimization #22

emduc opened this issue Dec 1, 2021 · 0 comments
Labels
security issue A bad thing...

Comments

@emduc
Copy link
Contributor

emduc commented Dec 1, 2021

The cryptographic function used to encrypt ballots is deterministic, ie. two encryptions of the same ballot will be equal, and the key is public. Therefore using a decrypted ballot it's possible for an attacker to re-encrypt it and see who submitted it. This is a problem only for votations with either few participants or where ballots are mostly unique (eg. with a text question)

Possible mititgations:

  • Use a random seed when encrypting the ballot that would not be shared during decryption (could use the new padding of ballots)
@nkcr nkcr mentioned this issue Jul 5, 2022
41 tasks
pierluca pushed a commit that referenced this issue Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security issue A bad thing...
Projects
None yet
Development

No branches or pull requests

2 participants