MailClad Architecture for open-systems open-source E-voting

Requirments for any Voting System

Voter Related Issues

Privacy - voters need to remail Anonomous

Protected from coercion - such as from a workers Union that might wish to verify someones vote.

Verify - there vote is counted.

Protected from physical intimidation at a polling station.

Must be allowed one vote and no more then one vote.

Human Related Issues

Humans from any single organization can not be trusted.
*   (I assume some small centralized over site by several opposing parties is safe)

Digital related Issues

Exposed Computers can not be trusted. (such as at polling stations)

Communication network can not be trusted.

Any cryptographic system based on Primes can be cracked with sufficient CPU power, or Quantum computers.
*   This covers all DES, AES, RSA, PGP and public key systems

Protection from Automated Attack is one of the most important issues.
*   This includes viruses, worms, or any kind of software based attack.

Other related Issues

The entire process be open to scrutiny, accountablity and tracablity.

We should assume that the entire design of the system is known to all attackers

Should be able to use existing "Commercial off the Shelf" COTS as most government organizations call it. Basically should be able to run on PC's, Mac's or what ever local municipalities have around.
*   It seems most of the commercial companies doing E-voting are focused on the "Machine". The Artistic styling of the box and getting large markups on them. But the box is just a thin veneer over the real product, the Software and it's system that is much more important then a pretty box.