Voting fraud... using VB?
From WIRED:
A government watchdog group is investigating allegations made by a Florida programmer that are whipping up a frenzy among bloggers and people who believe Republicans stole the recent election.
Programmer Clint Curtis claims that four years ago Rep. Tom Feeney (R-Florida) asked his then-employer to write software to alter votes on electronic voting machines in Florida...
It goes downhill from there.
A transcript of the programmer's testimony is here, where I left the following comment. Either the comments are moderated or there was an error, but here's the comment:
This would have to be the most amateurish attempt at voting fraud imaginable.
I mean, if you read 'Undocumented DOS' you'll hear sordid tales about MS XORing assembly code to prevent walking through it with a debugger, or jumping into the middle of an assembly language instruction because the destination byte was itself an instruction as well.
Now, we're to believe that voting fraud was contemplated using something as high-level, pedestrian, and "beginner's-language" as VB? Somehow I have a great deal of trouble believing this.
One would think they would not want to get caught, and they would not want to use something like VB that just about anyone could notice and understand. And, one would think they'd invest a bit more than five hours in the attempt. Instead, they'd use some of the ASM tricks described above, wiping the code and the memory and the disk where it was all stored just in case.
Since Curtis' code didn't do those same tricks, perhaps performing a detailed analysis of everything that was ever stored on the hard drives might be useful.
I also find it a bit difficult to believe that they would just blab their plans to someone who they hadn't, for instance, already compromised.
While there are certainly big problems with eVoting, I wouldn't put much faith in this story unless solid evidence is provided.