California to Start Review of Voting Machines
An anonymous reader writes "California Secretary of State Debra Bowen just announced details about the previously discussed 'top-to-bottom review' of almost all voting and counting systems used in the state. The team features big names in e-voting security: David Wagner, Matt Bishop, Ed Felten, Matt Blaze, and Harri Hursti, among others. Vendors have time to submit their machines including documentation and source code until July 1st or face severe restrictions, including decertification, for the 2008 elections. Scheduled to start next week, the review will include a red-team attack and going through the source code."
...But it's about time that electronic voting machines were beta-tested!
Well, back to rejecting software patent applications.
The last 2 elections were the beta.
"There are more things in heaven and earth, Horatio, than are dreamt of in your philosophy."
Ballot materials are "delivered" without proof. Even the moment to cast a ballot should be a postal duty. So-far, they can't say if mail was delivered or not when using the non-stamped commercial mail-meter rate. Every certified mail delivery of a vote from a person should be counted once by the postal Clerk in Record of the Direct Treasury Account. A network would facilitate a real-time audit of the vote; emphasizing between the debt to cast a vote in one's favor in valuation of their debt: a citizen-subject as opposed to a Citizen, not confused with a denizen or a national.
How will the state ensure that these machines will be identical to those used on election day? Will random voting machines be checked with similar precision during the elections, or what guarantee do we have that these machines will not have been tampered with through "enhanced" source code? I had a glimpse at the FAQ but could not find any information on this, perhaps someone has some pointers?
For this same reason, Consumer Reports and other reviewers buy products anonymously from stores instead of receiving them from vendors, due to previous cases in which the process (such as that intended with the voting machine review) has been taken advantage of.
parasight.de
Voting machines provide no advantage, other than obfuscation of possible/probable tampering and errors. Code reviews are a waste of time. Bring back paper. Non-tangible bit-flipping to register votes will never be sufficiently accountable.
At VERY minimum, institute scantron (filled in boxes on paper) voting.
...now introducing ballot V1.0, with enhanced security!
We are all just people.
Voting machines provide no advantage
Electronic voting machines are in virtually every way superior to paper voting machines.
They prevent you from accidentally submitting an invalid ballot.
They can be updated with a correct ballot much easier than actually printing ballots.
They can more easily accommodate voting by the disabled.
They can randomly display the list of candidates, eliminating the 'first ballot position' advantage.
What does NOT have many advantages, and has several disadvantages, is electronic vote-STORING machines. We definitely don't want any of those. But as long as the voting machine kicks out a voter-readable paper ballot, we don't really even need to know the software it's running. Anything nefarious will be obvious on the ballots.
paintball
Anyone know what the rules for freedom of information apply here? Could these rules be used to examine the source code for flaws?
My little Linux and tech blog
I appreciate California's effort to verify that their electronic voting machines work. I have developed an economic process for certifying electronic voting machines.
1) Determine if the voting machine produces a voter-readable, paper ballot.
2) Determine if this ballot is the OFFICIAL voting record.
3) If 1 and 2 are true, then the machine is good. If not, it's not.
There you go. Why do people insist on making easy problems hard?
paintball
If they pull out of California because of that, they may as well just quit the election systems game altogether. It's the largest market, and more importantly, when California does significant things, other states very often follow its lead, for better or worse.
Not, mind you, that I'm saying it's a bad thing for Diebold to get out of the market. (Which it's been reported they're considering doing anyway.) Don't let the door hit your ass on the way out, I say to them.
There is no need to see the source code for this software.
/.ers like to equate secure voting machines with open source. I like open source, but trying to inject it in this issue is foolish. It is irrelevant whether the voting machine uses open source software. Either it meets the spec, or it doesn't.
There is only one specification for a secure voting machine, and it is easy to test. There is no need to see the source code. If the machine meets the spec, it is a secure voting machine. Otherwise, it is not, and should not be certified.
Here is the specification:
1. The voter votes on the machine.
2. The machine prints out a ballot.
3. The voter checks the ballot for accuracy, then deposits it in the ballot box.
4. Ballots in the box are tallied for the official vote count.
Simple, easy, secure, reliable, and recountable. There is no need to see any source code.
A voting machine which doesn't meet this spec is not secure. It doesn't matter how many times you check the source, the machine will still not be secure. An "open source" voting machine which does not meet this spec is not secure.
If you had super powers, would you use them for good, or for awesome?
As one of the people involved in the crafting of the North Carolina law and supporting Joyce's lawsuit, I can clarify a bit. We suspect Diebold pulled out of North Carolina not because of the source code escrow issues (which they claim to have complied with in Georgia) but because the CEO of each voting company had to sign a legally binding document saying that the source code his company installed on our machines was the same code that would be placed in escrow and provided to the examiners. On the day this document was due Diebold pulled out of the state, sending a "helpful" letter to the State Board of Elections offering to help "reform" our newly-passed law.
-jdm
FOIA requires access to public records. It's possible that source code could be defined as a public "record," though it might be stretching the definition. "Records" are defined as tangible documents, which could certainly include computer files, but it seems to me that the govt would argue that voting documents and results are "records," but source code is part of the process by which the records were created rather than the records themselves. Besides, wouldn't this open up all source code used by federal agencies, including MS Word, assuming they use that to generate documents that are "records"?
Another problem is that the law only applies to federal agencies, though states may have their own laws that require similar public access. Since voting machines and procedures are the responsibility of state governments, the federal legislation wouldn't apply.
Frankly, I think we need new federal legislation here.
Hmm. One could almost do this with a piece of paper!
If only there was a way to mark a piece of paper with the candidate's names and then have a box next to each!
And perhaps some sort of paper marking implement to be given to the voter such that they may indicate their choice...
I fear such technology may be beyond us.
You can make a very nice vote-printing machine (rather than a vote-counting) machine, with all kinds of standards to make sure the questions are easy to read (or hear), that the answer that you put down is actually associated with the question that is on the screen, and that you can only put down ONE answer per voting question.
The resultant ballot sheet should contain a list of the items that you voted on, with your answer easily readable next to each item (using a machine AND voter-readable font, since having a separate machine-readable code would make the voter-verification worthless).
If anything looks fishy, the voter tosses the ballot into the shredder & gets a new blank one.
Manual recounts would be a helluva lot easier (no hanging chads, no wondering what a stray mark covering two ovals means, etc).
As the grandparent says, there's quite a few benefits that are possible by designing a solid system for printing votes, but using the computers to count the votes is really problematic.
Secretary of State is an elected position in California, and Debra Bowen got elected last November, so she hasn't been in place long. Previously she was in the state assembly and then state senate, where she was one of the influential people on open government, open records, and privacy issues, and made a big issue of doing something about the voting machine problems. I gather there are other issues where some people passionately hate her, but for the most part she's been viewed as an honest politician rather than one of the machine players. She's also an advocate of voting alternatives such as Instant Runoff and proportional representation in general.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Machine counting of votes is also sketchy. The big controversies in the 2004 election weren't about direct-recording machines, they were about the automated ballot counting machines. Unless you have a policy in place to require that the paper ballots be retained after scanning (rather than being destroyed) and a way to force a manual recount if *anyone* suspects machine tampering, you really haven't gained anything.
Someone on Slashdot once suggested separating ballot sorting from ballot counting. Put the ballots in a sorting machine and then use a dumb counting machine to count the sorted stacks. That's a much better plan (as long as the counter checks the stack to verify that it's sorted).
-- The act of censorship is always worse than whatever is being censored. Always.