You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only one issue submission today. Sadly not very high quality though (in our opinion). The report suggested a new vote-buying vector, if we implemented a particular proposed solution (…to another known hypothetical attack, which we find far more interesting). There are a number of problems with the submitted vote-buying issue though. We wrote up a detailed response. You can see the submission & response right after it, both here: Vulnerability of "Recycled Verification # Attack" #115 (comment)
Since opening yesterday, we’ve had 3 submissions, 2 from @cjackett & 1 from @phish. Sadly phish’s is outside our eligibility criteria for HACK SIV prizes (see detailed content rules: https://hack.siv.org/rules).
Seems that as of right now, 100% of our 1/2 of the prize allocation is heading to @cjackett. But 3.5 days remain! No offense to them, but they could use more competition! Now’s your chance!
Tomorrow morning, in-person DEF CON begins. Very excited. Find us at the Voting Village. We’ll also launch a mock election. Suggest questions if you have ideas!
Again, even before Live Mock Elections begin, you are invited to:
a. Search for vulnerabilities in the SIV Protocol, the foundation of the Secure Internet Voting system - https://docs.siv.org/technical-specifications. After all, if the blueprint of the system is not sound, the implementation can’t possibly help.
b. For a lighter start to the protocol, here’s a simpler illustrated overview: https://siv.org/protocol
c. And of course, you can run the SIV code on your own machine for local testing: https://github.com/siv-org/siv
So, can you find novel ways to…?
Vote multiple times
Change someone else's vote, without detection
Destroy a vote already confirmed submitted
Learn how someone voted, without their help
Learn other personal info about voters
Bonus: Convince us of major score updates to docs.siv.org/compare
Here's today's update:
Only one issue submission today. Sadly not very high quality though (in our opinion). The report suggested a new vote-buying vector, if we implemented a particular proposed solution (…to another known hypothetical attack, which we find far more interesting). There are a number of problems with the submitted vote-buying issue though. We wrote up a detailed response. You can see the submission & response right after it, both here: Vulnerability of "Recycled Verification # Attack" #115 (comment)
Since opening yesterday, we’ve had 3 submissions, 2 from @cjackett & 1 from @phish. Sadly phish’s is outside our eligibility criteria for HACK SIV prizes (see detailed content rules: https://hack.siv.org/rules).
If you haven't already, check out yesterday's full update - HACK SIV — Tue Aug 6th — Launch Day — End of Day Report #179
Seems that as of right now, 100% of our 1/2 of the prize allocation is heading to @cjackett.
But 3.5 days remain! No offense to them, but they could use more competition! Now’s your chance!
Tomorrow morning, in-person DEF CON begins. Very excited. Find us at the Voting Village. We’ll also launch a mock election. Suggest questions if you have ideas!
Again, even before Live Mock Elections begin, you are invited to:
a. Search for vulnerabilities in the SIV Protocol, the foundation of the Secure Internet Voting system - https://docs.siv.org/technical-specifications. After all, if the blueprint of the system is not sound, the implementation can’t possibly help.
b. For a lighter start to the protocol, here’s a simpler illustrated overview: https://siv.org/protocol
c. And of course, you can run the SIV code on your own machine for local testing: https://github.com/siv-org/siv
So, can you find novel ways to…?
Bonus: Convince us of major score updates to docs.siv.org/compare
Happy Hacking! :)