How Random Babbling Becomes Corporate Policy (t3knomanser) wrote,
How Random Babbling Becomes Corporate Policy

Other voting notes...

Any evoting system must:
  • Be implemented in 100% ANSI code- no Java, .NET, etc. (caveat: these could be acceptable, but would require a custom, open source VM/runtime-environment). It seems more desireable to implement in C++ however.
  • Provide human verifiable trails at _every step_
  • Provide strong encryption
  • Be physically, as well as logically, secure.

I'm trolling around on Sourceforge, looking at some of the voting related offerings, and seeing alot of Java/.NET ones. This is unnacceptable, because you are importing security holes from your VM/runtime vendor. There are open source implementations of both Java and .NET, but most are in pre-alpha states, or at best, beta. Any software leveraged by the voting system must be mature. For example, running a C++ voting system on embedded linux, using X to provide GUI is acceptable, provided a mature version of embedded linux is used. This software has already been tested extensively, and most major security holes have been fixed.

The back-end O/S must be OS, which excludes using Windows or Mac on the PC- every step of the functioning must be verifiable, testable, and modifiable, including the basic communication with the hardware.

  • Strange Things People Say About Me (to my face)

    Recently, I've been at the center of a trend. That trend is complete strangers asking me "Are you ____?" A quick summary. For example: Are you…

  • Writer's Block: If I could find my way

    -10,000 years, at minimum. Tomorrow is always better than today, especially when you can't fact-check.

  • Bob Morlang

    When I was working at Tri-Mount, we had these camp trucks. They were army surplus, and while they could take a beating, they only sort of worked. And…

  • Post a new comment


    Comments allowed for friends only

    Anonymous comments are disabled in this journal

    default userpic

    Your IP address will be recorded