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

Docs: coercion resistance vs receipt-freeness #190

Open
dsernst opened this issue Aug 9, 2024 · 1 comment
Open

Docs: coercion resistance vs receipt-freeness #190

dsernst opened this issue Aug 9, 2024 · 1 comment

Comments

@dsernst
Copy link
Member

dsernst commented Aug 9, 2024

One other nit: https://docs.siv.org/compare conflates coercion resistance and vote selling. These are actually two different things, and have different definitions in the literature (see the Bernhard SOK linked in my original comment).

Coercion resistance = I cannot collaborate with an attacker to prove the way I voted. E.g., an attacker sits with me while I'm voting to verify that I selected their options. Receipt freeness (Vote selling resistance) = I cannot prove the way I voted after the fact.

A system might actually be receipt free, and not coercion resistant. Consider a system that, when a user submits a vote, does not allow the user to re-vote or spoil the ballot, but also provides no receipt or method of verification. That system will be receipt free -- the voter has no way to prove after the fact that they cast a ballot in any particular way -- but not coercion resistant because an attacker watching them vote can confirm how they're voting.

Originally posted by @mspecter in #181 (comment)

@arianabuilds
Copy link
Member

arianabuilds commented Aug 29, 2024

Entry Summary for HACK SIV @ DEF CON 2024

Thanks again for participating! This submission earned $45.35 from SIV and $60.00 from the public vote, for a total of $105.35.

Here's what we noted in our evaluation:

What's interesting about this submission

  • Links to reference material in published paper, going into more depth

What takes away from it

  • The table is meant to be a high-level summary (eg it doesn't break out Accessibility into Mobility, Vision, Motor, etc)
  • Unclear how much the added complexity really helps, or if it would make it harder to read the table

Issue to track getting paid: siv-org/hack.siv.org#11

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

2 participants