Diebold Flops in Alaska
lukej writes "From the Anchorage Daily News, During yesterday's preliminary and ballot measure election across Alaska, Diebold built voting machines failed to 'phone home' causing a hand recount. As a party spokesperson said:
"I can say there are many systematic problems with Diebold machines that have been identified in many contexts."
Additionally, the state itself has mandated some hand counts of all electronic results, and the Democratic Party is simply suggesting voters request paper voting."
Keyword is contract and how long they can milk it.
I'm part of the Open Voting Consortium and we've been proposing a system in which the voter uses a machine to produce a paper ballot. That ballot *is* the ballot, not some copy, not some receipt, but the actual ballot. And it isn't good until stuffed into a ballot box.
The paper ballot is the core - it's in a form and font easy for machine readers to read, but it can also be read by people.
Now, that vote-printer machine can be any machine that has an interface appropriate to the needs of the voter - such as audio driven for sight impaired voters. (A ballot reader would be available to do an audio readback.)
Our proposal is to do this, plus a canvassing system (that's the part that aggregates the precinct counts into the grand totals.)
And we feel that *all* code, and all machinery, should be inspectable and testable by anybody who wants to run a test (and they should be able to publish their test results.) That's one step short of full open source - which doesn't mean that the code couldn't also be open source under one of the licenses.
It is a mistake to think of these things as a software issue - it involves machines (even if they look and smell like PC's, although I personally tend to prefer smaller/lower power engines like the WRAP or Soekris machines) and procedures, lots and lots of procedures (like what to do if a voter walks out in the middle of casting his/her vote - there are laws that say what to do, and they, of course, vary from state to state and even county to county.)
But it is harder to do than one thinks - the machines themselves can't just be any old junk PC. They need to be robust in the face of voter use and tampering behind the scenes. And they need to have lots and lots of places where they can be locked-down (often using things as simple as lead-and-wire tamper seals) to prevent hanky-panky by warehouse or precinct people.
They need to be power-conserving (imagine a precinct with a single circuit breaker/fuse and a flakey or non-existant ground, and that the voting is occuring during a thunderstorm.) UPS's are a pain - they have a high failure rate and given that they often contain a lead-acid battery, are neither lightweight nor quite innocent should they leak. And it's important to keep the fire marshall happy.
And printers are a pure pain in the rear - they can draw a lot of power and are generally the most failure prone part of the system.
And there are lots of legal requirements - like protecting the privacy of the vote. You can, for example, potentially reconstruct which voter voted which way by looking at things like sequencial files used for audit/error-detection or for ballot tallies.
And the stuff has to be easily configurable en masse - counties tend to need hundreds, thousands of these things, and they better all be the same. And they need to be able to be transported by folks who aren't necessarily gentle and set up by people who make your grandmother look like a tech support wizard.
We were planning on doing a project to produce a reference model for such a system via the University of California (multi-campus project with UC Santa Cruz in the project lead position) but we got cut out of California's HAVA (Federal voting act) funding when the previous California Sect'y of State got caught up in a brouhaha on other matters. It's still worth doing - every state would benefit.
http://alternet.org/blogs/video/40755/
Summary --
Computer programmer Clinton Eugene Curtis testifies under oath before the U.S. House Judiciary Members in Ohio. Stephen Pizzo writes:
A partial transcript:
Are there computer programs that can be used to secretly fix elections?
Yes.
How do you know that to be the case?
Because in October of 2000, I wrote a prototype for Congressman Tom Feeney [R-FL]...
It would rig an election?
It would flip the vote, 51-49. Whoever you wanted it to go to and whichever race you wanted to win.
And would that program that you designed, be something that elections officials... could detect?
They'd never see it.
You miss the point. He could write a 'pretty good' voting machine in a day (Or not, that's not the point). Diebold, with all their money and years can also come up with one that is 'pretty good'. It should be perfect. Therefore, on a time/money per quality of product basis, Diebold are worse than useless.