Re: code validation?

From: Edward Cherlin <cherlin_at_pacbell_dot_net>
Date: Wed Feb 23 2005 - 00:57:12 CST

On Tuesday 22 February 2005 13:16, Arthur Keller wrote:
> How easy is it to "reverse engineer" a body of code to match a
> hash, even one that's broken? Would listing the code length
> also help?
>
> The CDs should have some suitable chain of custody.

Actually, the CD should be published so that it can be widely
tested. We can verify CDs before using them, so we don't have to
trust a chain of custody.

> One outstanding question is how we prevent the hash-code
> displaying software from lying and giving the published
> answers even if the code doesn't match.
>
> Best regards,
> Arthur

Bear in mind that the hash algorithms are public, and any
observer can test the CDs on a computer with their own set of
software. We don't have to trust either the CD or the voting
computer. I have suggested that the law should require voting
software used in any election to be certified some set number of
months before the election, so that any problems can easily be
uncovered in advance.

-- 
Edward Cherlin
Generalist & activist--Linux, languages, literacy and more
"A knot! Oh, do let me help to undo it!"
--Alice in Wonderland
http://cherlin.blogspot.com
_______________________________________________
OVC discuss mailing lists
Send requests to subscribe or unsubscribe to arthur@openvotingconsortium.org
==================================================================
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
==================================================================
Received on Sun Feb 27 17:17:11 2005

This archive was generated by hypermail 2.1.8 : Sun Feb 27 2005 - 17:17:13 CST