Sequoia Voting Systems has inadvertently released the SQL (Structured Query Language) code for its voting databases. The existence of such code appears to violate Federal voting law. Read the announcement after the jump, just as received on the Open Voting Consortium mailing list earlier today.
More to come, once we get a chance to dig in and see in full detail what Sequoia gave us.
Disclosure: I am a founding member of OVC.
Update: The files were not vandalized. They load into the original database software without problems. Investigation of the SQL continues.
[OVC-discuss] Something really big: Sequoia source code, free to download and study, no NDAs.
00:49 (14 hours ago)
Folks, you'll love this.
Sequoia blew it on a public records response. We (basically EDA) have election databases from Riverside County that Sequoia insisted on "redacting" first, for which we paid cold cash. They appear instead to have just vandalized the data as valid databases by stripping the MS-SQL header data off, assuming that would stop us cold.
They were wrong.
The Linux "strings" command was able to peel it apart. Nedit was able to digest 800meg text files. What was revealed was thousands of lines of MS-SQL source code that appears to control or at least influence the logical flow of the election, in violation of a bunch of clauses in the FEC voting system rulebook banning interpreted code, machine modified code and mandating hash checks of voting system code.
I've got it all organized for commentary and download in wiki form at:
This is the first time we can legally study a voting system's innards without NDAs or court-ordered secrecy.
Join the fun :). First goal is to prove that Sequoia did in fact vandalize the data files by stripping the MS-SQL headers - if so that will affect other public records inquiries against Sequoia.
Second goal: what does the code do, what are the security implications, is it as big a violation of the FEC rulebook as it appears?