PO Box 531  •  Durham,NC 27702  •  Telephone: (919) 419-8311  •  Fax: (919) 419-8315

Tuesday, November 29, 2005

Tennessee to purchase black-box voting machines

Posted by R. Neal

Jumping on the "Free-Federal-Funding-for-Black-Box-Voting-Machines" bandwagon, Tennessee is set to spend $25 million on new electronic voting equipment. Except we haven't had the kinds of problems they had in Florida and Ohio, and nobody can explain what's wrong with our current equipment or why we need new equipment. Sure we have a bunch of Democratic Congressional districts, and a so-called Democratic governor. But we went for Bush twice in a row. What's the problem? Seems like the $25 million could be better spent on TennCare or Katrina reconstruction.

In related news, poor old Diebold says they won't sell their black-box voting machines to those mean old election officials in North Carolina who insist on reliability and accountability:
Diebold Election Systems is worried it could be charged with a felony if officials determine the company failed to make all of its code -- some of which is owned by third-party software firms, including Microsoft Corp. -- available for examination by election officials in case of a voting mishap.

[..]

The dispute centers on the state's requirement that suppliers place in escrow "all software that is relevant to functionality, setup, configuration, and operation of the voting system," as well as a list of programmers responsible for creating the software.

That's not possible for Diebold's machines, which use Microsoft Windows, Hanna said. The company does not have the right to provide Microsoft's code, he said, adding it would be impossible to provide the names of every programmer who worked on Windows.
Who knew Windows had election specific functionality buried deep in the operating system? That's just about the stupidest argument I've ever heard. What are they hiding?

I seriously doubt that NC state law requires deposit of the source code for the operating system or any other software not written by the election system vendor. No escrow agreement I've ever seen or heard of requires the operating system to be on deposit. That would be ridiculous. If there's some ambiguity or flaw in the statute, I'm sure it can easily be fixed.

Software escrow is common in many industries, for the purpose of audit similar to this case, or for business continuity in the event of vendor default or bankruptcy. Software vendors understandably don't like it because they want to protect their source code and proprietary trade secrets from competitors and other prying eyes, but they routinely do it. And it certainly seems appropriate for something as critical as election systems.

Besides, hackers and computer science researchers already had a look at their source code when Diebold was too stupid to secure their FTP servers. Researchers at Johns Hopkins analyzed the software, and concluded that it had serious security flaws. California officials decertified the system just prior to the 2004 elections after problems with the machines surfaced in California, Maryland, and Georgia. And don't forget, the president of Diebold, an Ohio company, said in 2003 that he was "committed to helping Ohio deliver its electoral votes to the president next year". And we all remember how that turned out.

Anyway, I'm not so paranoid yet as to believe that Diebold is an evil company out to systematically rig elections. Heck, I trust their ATMs without reservation. But black-box voting machines have too many problems, and Diebold is the dominant vendor in the industry. They should be leading the way with secure, reliable, and verifiable equipment open to inspection. At the very least these systems should have a paper audit trail that can be independently verified by human eyes. Otherwise, there is no overall accountability and "recounts" are a joke.

OK, then.
posted by R. Neal at 8:34 AM | Email this post | Post a Comment
2 Comments:
Blogger Dave said...

"That's not possible for Diebold's machines, which use Microsoft Windows, Hanna said. The company does not have the right to provide Microsoft's code, he said, adding it would be impossible to provide the names of every programmer who worked on Windows."

WTF? No one's asking them to provide the source code for Microsoft's APIs. If I develop a class, and the client who purchases the class wants to see the source code, can I say that is impossible because I don't have the code for the underlying objects? No. That's just plain stupid. In fact, I find that insulting. Every time someone from Diebold opens their mouth, they appear more and more ignorant.

12/02/2005 11:14 AM  
Blogger Moonkat said...

Frankly, if we (the people) are buying the machines, I think we should insist on access to all vote-counting source code. Also, anyone who hasn't yet watched "Hacking Democracy" should put it high on their "must see" list. Excellent documentary about the problems inherent in electronic black box (pig in a poke) voting machines.

8/24/2007 11:53 AM  

Post a Comment

Return to Facing South's main page

Southern News Update

Who Are These Folks?

CHRIS KROMM blogs three days a week for Facing South. Chris is Executive Director of the Institute for Southern Studies and publisher of the Institute’s award-winning magazine, Southern Exposure.

SUE STURGIS blogs four days a week for Facing South. Sue is the Institute’s Editorial Director and a former reporter for The Independent Weekly and The Raleigh News & Observer.

DESIREE EVANS blogs four days a week for Facing South. Desiree is a Research Associate at the Institute and former policy analyst for TransAfrica.

The views expressed on Facing South are those of the authors and not necessarily represent the views of the Institute for Southern Studies. The editors reserve the right to reject comments that are abusive, offensive, misleading, or that promote commercial goods and services.

Previous Posts