Feng Group
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Help
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

Your note will be visible on your profile and discoverable by anyone.
Your note is now live.
This note is visible on your profile and discoverable online.
Everyone on the web can find and read all notes of this public team.
See published notes
Unpublish note
Please check the box to agree to the Community Guidelines.
View profile
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
###### tags: `Reading sessions` [toc] # 2023 <https://e-vote-id.org/e-vote-id-2023/> ## [**Faster Coercion-Resistant E-Voting by Encrypted Sorting**](https://eprint.iacr.org/2023/837.pdf) * By Diego F. Aranha, Michele Battagliola, and Lawrence Roy. * **[LH]** The paper proposes a new variant of the Juels Catalano Jakobsson (JCJ) protocol for coercion resistant voting. JCJ is not very scalable due to its quadratic complexity. The paper improves the complexity to log-linear by encorporating a comparison-based sort as part of the tallying process. The main idea is to store registration data in binary form for each voter, and create a sort using circuits over encrypted bits. * The authors note their protocol could be improved further by possibly adopting a bucket sort, but this might be prone to a bucket overflow attack. Dimension of the credentials is also a problem as these are stored as encryptions of bits rather than whole strings. # 2022 <https://e-vote-id.org/programme-2022/> ## [**VoteXX : A Solution to Improper Influence in Voter-Verifiable Elections**](https://eprint.iacr.org/2022/1212) * By David Chaum, Richard T Carback, Jeremy Clark, Chao Liu, Mahdi Nejadgholi, Bart Preneel, Alan T Sherman, Mario Yaksetig, Filip Zagórski, and Bingsheng Zhang. * **[LH]** The paper aims to solve the problem of vote coercion and vote buying for online elections. The general idea is to introduce a set of trusted parties (called *hedgehogs* in the paper) that can *nullify* a vote. It assumes an untappable channel between the voter and the hedgehogs. * The voter has two public/private key pairs (for a yes/no vote respectively). If the voter has been coerced, they share their secret key for their true vote with the hedgehogs. The hedgehogs have a list of public keys, and construct another list containing $1$ if they know the secret key for the corresponding public key (pairwise), and $0$ otherwise. * The hedgehogs must prove they know the secret key for the voter among all public keys using a disjunctive ZKP. The constructed lists for each hedgehog are summed by the Election Authority (EA), who then subtracts them from the yes/no tallies to produce the final tallies. * Nullification can be performed in three ways: *cancel*, *cancel-toggle* or *flip*. *Cancel* nullifies a vote iff at least $t \geq 1$ entries chose to nullify it. *Cancel-toggle* nullifies a vote iff odd $t$ entries chose to nullify it. *Flip* nullifies a vote $x$ by computing $(x + y) \mod k$ where $y$ hedgehogs chose to nullify the vote and $k$ is the number of candidates (this is essentially randomization of the vote). * For the multi-candidate case, the voter may register $k$ key pairs. * Performance of the protocol appears to be quite good; nullification is the most work at $\Theta(HVT)$ given $H$ hedgehogs, $V$ voters and $T$ trustees. * The limitations of the paper are a (1) lack of security analysis and (2) a lack of a method for selecting trusted hedgehogs. The paper acknowledges (1) for future work and (2) is indirectly acknowledged by a future user study. It would be interesting to see the result of the user study and whether any problems with choosing hedgehogs arise in practice. The paper does also make a large number of assumptions, and whether these assumptions hold true in practice would be nice to see. ###### tags: ``e-voting`` --- ## [The Diffusion of Electronic Voting for Participatory Budgeting Projects: Evidence from Ukraine](http://dspace.ut.ee/bitstream/handle/10062/84324/13.pdf?sequence=1&isAllowed=y) * Dmytro Khutkyy * A study on the e-voting usage statistics among Ukrainian communities for participatory budgeting. * Some statistics data presented, but not very conclusive * The percentage of e-voting usage varies from 1% to 100%. * "The one definitely confirmed pattern of participatory budgeting e-voting diffusion in Ukrainian communities is that longer duration of participatory budgeting is associated with higher e-voting rates." ###### tags: `` `` ## [Time, Privacy, Robustness, Accuracy: Trade-Offs for the Open Vote Network Protocol](https://eprint.iacr.org/2021/1065.pdf) * Fatima-Ezzahra El Orche, Gergei Bana, Remi Géraud-Stewart, David Naccache, Peter Rønne, Peter Y A Ryan, Marco Biroli, Megi Dervishi and Hugo Waltsburger * It aims to address the robustness issue of OV-net by running the protocol in parallel * As the tallying is done on a smaller size, there is possible privacy leakage, but the authors show the leakage is controllable. * Other trade-offs are: an increae in comptuation and a statistical loss of accuracy. ###### tags: `` `` ## [Review Your Choices: When Confirmation Pages Break Ballot Secrecy in Online Elections](https://dl.acm.org/doi/10.1007/978-3-031-15911-4_3) * By James Brunet, Athanasios Demetri Pananos, and Aleksander Essex. * [LH] The paper looks at ballot secrecy from the network perspective. Namely, whether one could determine the candidate in an encrypted ballot from the TLS record length of the confirmation page. * The authors considered SimplyVoting, a Montreal-based online voting vendor and created their own server to mimic SimplyVoting's confirmation page, sending thousands of requests for analysis (one ballot per HTTP request between a client and a server). * 2000 ballots were cast across four candidates (including an "Abstain" candidate). A Multinomial Naive Bayes Model is used to predict the candidate given a requests byte length. The overall result is an 83% predication accuracy over all candidates. The highest accuracy is 100% (for "Abstain"), whilst the lowest is 58%. * A relaxed definition of privacy is also considered by the authors for subsets of candidate combinations. The authors show that, up to 12 combinations, all ballots were associated with at most 11 possible ones. This means we could figure out at least one combination of candidates not chosen by a voter. * Multiple mitigations are proposed. * One is to generate the confirmation page client-side using Javascript (trivially avoiding the side-channel attack). This is done by Swiss Post. * Another is to pad the response. This could be either padding the response to be of fixed-length, or adding a randomised amount of padding. For uniformly randomised padding, the authors note that some ballots could still be clearly identifiable (e.g. ones that vote for a candidate with a long name that receive the maximum amount of padding). The authors briefly consider padding with a Gaussian distribution to try and minimise these clearly identifiable ballots, leaving the exploration for future work. ###### tags: `` `` ## [**An Analysis of the Security and Privacy Issues of the Neovote Online Voting System**](https://link.springer.com/chapter/10.1007/978-3-031-15911-4_1) * By Enka Blanchard, Antoine Gallais, Emmanuel Leblond, Djohar Sidhoum-Rahal and Juliette Walter * [LH] The paper looks at the security of the Neovote online voting system. Neovote was used for 3/5 of the primary elections in the French Presidential election in 2022. * Many aspects of the system were found to be insecure. There is no end-to-end aspect to check the integrity of ballots or the tally. The vote verification step appeared to disappear or was removed entirely. * The ballot box and receipt are not digitally signed, enabling a few attacks. One could spread a fake ballot box or create a fake receipt that has arbitrary hashes in it. If an adversary has access to all receipts, they could deanonymise a constant proportion of the ballots for each candidate. ###### tags: `` `` ---

Import from clipboard

Paste your markdown or webpage here...

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template has been removed or transferred.
Upgrade
All
  • All
  • Team
No template.

Create a template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

Slide Example

API Docs

Edit in VSCode

Install browser extension

Contacts

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

Note content is identical to the latest version.
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully