In a paper election, you have a chain of people who supervise each other. Depending on where you live, you can volunteer to be part of that and see it for yourself.
In code, you have no insight into what actually happens.
In a paper election, you have a chain of people who supervise each other. Depending on where you live, you can volunteer to be part of that and see it for yourself.
In code, you have no insight into what actually happens.
Let's say you encounter a mob society that is convinced that there is a very high risk of election fraud and will apply unnecessary scrutiny to votes, a little rip in the paper or ink not matching standards.
trivia: did you know that a tear in any of the pages of your passport renders it invalid?
Believe it or not there is a chain of people who supervise each other for this e-voting system as well. Anyone can volunteer to be part of it as well.
How can I volunteer to see the bits in a voting machine's RAM?
Logic tests only show that the machines worked correctly as of the logic test. It's easy enough to design them to behave correctly in all cases except actual elections.
> It's easy enough to design them to behave correctly in all cases except actual elections
How? Any possible scheme I can think of that could theoretically allow a tabulation machine to behave differently on audit ballots than it does on real ballots, can also theoretically be mitigated via audit procedures.
> How? Any possible scheme I can think of that could theoretically allow a tabulation machine to behave differently on audit ballots than it does on real ballots, can also theoretically be mitigated via audit procedures.
An audit will only mitigate that if a) you have paper ballots you can check, b) the audit happens very soon after the closing of the polls. If an audit takes place a month later, that's a lot of time for the elections administration to create all new ballots to replace the originals with, so the audit has to come very soon after the election.