 |
 |
 |
My Stance
Research
The Voter Program
This page is a collection of specification ideas I have on the program used to track votes. I have started working on the actual source code for this. I will make it available shortly for review by anyone who wants to. But here is what I have so far for the general overview of it.
Each voter, when they go in to get their ID or Drivers licensed (does not necessarily need to be any Real ID stuff), the DMV office that they enter will have a pin pad similar to the ones that are found at most banks. When the person gets their ID, they are asked to enter a 8-10 digit pin number. This pin number, along with their SSN and Full Name will allow them to login to the voting system from anywhere.
The DMV office, or anyone else, will not have access to, nor shall ever ask for this PIN number. If at any time this PIN number is leaked. This users account in the system must be immediatly disabled and the user should have to come in an reset it. They should be required to prove who they are before they have any access to resetting this.
At the time of this entry, all non-personal information collected by the person along with a hash of their PIN number and SSN will be stored on this server, and then replicated to the rest of the system. There will be a random ID also created for the user, which can be used by other systems, other people, the government, polling stats, etc... This ID number can be used to view the voting history of a person, along with possible demographics about the person. As long as this information is non-personal, and cannot track information on the voter back to the actual physical person. The voter will not know what this number is.
At NO TIME EVER shall any other individual, government entity, computer system, agency, officer, etc... have or want access to the voters PIN number or their personal information. At no time shall any other system access this system in any other way other then with the secondary random ID generated for the voter. I.E. You can to statistical reports about the voter, but you should never be able to access who this person really is.
Security
Many people will be worried about the security of this system. I think this can be easily handled. We already do major financial transactions online. And there is very little fraud in these systems. Now the problem that we face is "fishing" issues that make people think they are going to thier bank. This is similar to the fake e-mails you get asking you to verify your bank account information.
This system will never ask people to change information about themselves. If it does, it will only ask them to come, in person with proper documentation, to their local DMV office, log into a secure kiosk there and change thier information. This should not limit their ability to go online and change their information at their own will.
This system should be built so that it can be easily modified by any user. The change procedure should go as follows:
- Someone suggests a change. This includes a copy of the source code.
- The source code, and the change is put to vote as any other agenda item is. If a super-majority of the people like the change (>65%) then the program will automatically inject the code - as it was voted on. There will be no further modification of the code once it hits the Vote stage.
- The source code, and all comments are fully viewable by all voters.
- The change should only affect 1 specific item. It should not be a global change. It should only be minor steps.
- At any time, any change added or modified from the original version can be removed. With a simple majority vote. It will be automatic once the vote is complete.
Some more thoughts on this.
I have been trying to come up with some of the best ideas I can for this. One thing that should occur with this system is data replication and verification. This should occur automatically between all computers hosting the software for this system. This should happen when users request stuff, and also randomly in the background.
Each computer, when a new item is created, or when information is requested, should request the information from 3-10 random other computers. It should then verify that the information is the same on all. If one is different, it will then notify that one server to delete it's copy of the information.
Once the server with corrupted\incorrect information is requested to delete the record, it should automatically delete it, and then randomly pick 5-10 other computers for a copy of the informatioin.
What this should accomplish is this. If you want to hack the information, you will probably have to hack several hundred computers at once that are located all over the place.
Any questions, comments, opinions, please contact me at: gjconely<at>gmail.com
I do not know everything. If people have any real good insight or information that I am missing, please sent it to me.
All comments, suggestions, questions, etc... may, and probably will, be posted on this site. I will exclude your name if requested.
If you have the time or resources to help, please feel free to Donate