How Can You Test An E-Voting Machine For Malfunctions If You Don't Get To Test The Machine?
from the just-wondering dept
Now that Florida's governor has admitted that e-voting machines without a paper trail are not such a good idea (though, the optical scan machines he wants to replace them with have their own problems), you would think that Florida would be all for a thorough investigation into the problems of the old machines. Perhaps not. Remember Sarasota, where a bunch of votes appear to have gone missing? In the lawsuit over this, the judge denied the request to see the e-voting software source code, saying there needed to be more evidence that the machines malfunctioned first. At the same time, however, the Department of State in Florida has been trying to commission an "independent" study of the e-voting software, and even spoke to Ed Felten about joining the team. He's listed as one of the investigators, though he actually declined to take part. Why? Well, it turns out that they want the investigation to take place without actually letting the experts view the working software or the e-voting machines. Instead, it only wants to give them the source code and let them comb through the source code alone to try to figure out where the malfunction could have occurred. It's great that at least some experts are finally getting a chance to look at the source code, but it makes you wonder why all of these e-voting security tests always have strict limitations on them. If they really wanted to know what the security vulnerabilities are, shouldn't they make the test much more complete?