Wisconsin Requires Open Source, Verifiable Voting
AdamBLang writes "Previously covered on Slashdot, Wisconsin Governor Jim Doyle today signed legislation that "will require the software of touch-screen voting machines used in elections to be open-source. Municipalities that use electronic voting machines are responsible for providing to the public, on request, the code used." Madison's Capital Times reports "the bill requires that if a municipality uses an electronic voting system that consists of a voting machine, the machine must generate a complete paper ballot showing all votes cast by each elector that is visually verifiable by the elector before he or she leaves the machine.""
[T]he machine must generate a complete paper ballot showing all votes cast by each elector that is visually verifiable by the elector before he or she leaves the machine.
And how do we know that the prinout matches whatever counter is incremented within the computer? Being open source makes it tamper-resistent, not tamper-proof. Would it not be easier to just use a paper ballot in the first place? Then any recount could be performed against the actual ballots cast, not as a spot check against computer (glitches|fraud).
Trolling is a art,
Paper receipts should be a no brainer, as should be open source software for voting machines. Too bad this isn't occurring in every state, yet. Or is it? I am an ignorant person about this topic. Someone enlighten me.
There seems to be (happily) no preclusion of printing bar codes indicating the choices underneath the names of the candidates. This should allow for rapid and accurate scanning and counting. Ballots can be verified by hand or other (possibly 3rd party) means to prove that the bar codes equal the name on the ballot.
This will speed up and make more accurate the counting vs. OCR of the candidates' names.
Unitarian Church: Freethinkers Congregate!
The article states that "any device used". To me that implies that each county is responsible for deciding which machine they use. Is the state making sure that any system used also uses a standarized format for the results?
Also, just because you publish some source, that is no guarantee that that was the source that went into creating the binaries that are being executed. Are they going to use a mechanism to verify that a vendor publishes the exact source? Are they going to force vendors to react to bugs found within a specific timeframe. After all, someone examining the source could find a problem and potentially use it as an exploit, this usually isn't an issue because you're banking on someone else also finding the problem and being open/honest about it, but for something like voting, is that good enough? It seems like a lot of focus is being given to it being open source, but is ignoring other software deployment issues.
Can someone explain why we can standardize street signs and the amount of sugar allowed in school lunches but we cannot get a standardized election system?
After the 2000 election debacle, we had money thrown at the states to "fix the problem." So we ended up with 35 different solutions.
A simple federal mandate - the voter must be verifiable, their vote must be able to be able to be authenticated after they leave the booth, in the event of a recount and the system can be fully audited. Instead, we have systems with no paper trails, questionable vendor operations, and seemingly contradictory election results.
We can make millions of secure stock sales, bank transfers and on-line purchases daily, and we cannot get a vote counted and auditable? The people who produced these machines should be fired for stupidity and forced to return our money.
Although that would work on incredibly stupid voters, simple intimidation usually works on them anyway.
Voters with half a brain cell copy, forge or borrow a receipt to show to the boss.
There's no voter name on the receipt, thus no way for the boss to know how YOU voted.
I don't see any sign that this bill requires the code to be open source. The bill requires it to be made public, but does it actually require the state to make it available under an open source licence?
The WIS quote only says that "the coding for the software that is used to operate the system on election day and to tally the votes cast is publicly accessible and may be used to independently verify the accuracy and reliability of the operating and tallying procedures to be employed at any election". For them to call this open source is bad enough, but for Slashdot to repeat this misunderstanding of the term is ridiculous.
The world has changed and we all have become metal men.
The existence of preference cycles in condorcet results is a pretty serious problem. Frankly, it makes it a non-starter as far as I'm concerned.
Wikipedia lists seven different algorithms for resolving cycles. Can you imagine TV news explaining to the average American how the set theory behind the Schwartz set method determines the President?
IRV may be flawed, but it's easily understandable, and a huge improvement on FPTP.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak