That goes to version control and logging. Done right, you know what software is in place at all times. Dominion does not do version control or logging properly AFAIK. Any change in version in any software between end of testing and end of the election cycle is a bust: election not certified.
Its possible to verify the checksum of installed and/or running software and compare it to a list of target software, and to do it repeatedly. Of course, none of this should be running on Windows or iOS or Android. Should be Open-Source software on the most open platform possible. No USB drive autorun. Strict logging and video monitoring of the few USB ports allowed. There are dozens if not 100s of obvious problems with the Dominion system.
Any system can be corrupted, but paper and thumb ink (with previously obtained ID) is the easiest to keep honest and a complex swiss-army-knife electronic system the easiest to corrupt. Keep an electronic system bare-bones simple and it could work. You have to make any complex reporting and forecasting modules external to and separate from the core tally functions, with zero data flow allowed back into the tally function. Any ballot-correction function must create one or more separate totals which are broken down by type. The separate totals must never mix with the core vote counting system, but forever remain independent streams with independent and clearly labeled causes for their existence.
To my mind, such as it is, any election software should be open sourced, with all affected parties sitting at the planning table, and every voter given access to the source code. Anything less than full open source or paper and inked finger will never be accepted by me as a legitimate election. Never.
That goes to version control and logging. Done right, you know what software is in place at all times. Dominion does not do version control or logging properly AFAIK. Any change in version in any software between end of testing and end of the election cycle is a bust: election not certified.
Its possible to verify the checksum of installed and/or running software and compare it to a list of target software, and to do it repeatedly. Of course, none of this should be running on Windows or iOS or Android. Should be Open-Source software on the most open platform possible. No USB drive autorun. Strict logging and video monitoring of the few USB ports allowed. There are dozens if not 100s of obvious problems with the Dominion system.
The devil is in the details.
Any system can be corrupted, but paper and thumb ink (with previously obtained ID) is the easiest to keep honest and a complex swiss-army-knife electronic system the easiest to corrupt. Keep an electronic system bare-bones simple and it could work. You have to make any complex reporting and forecasting modules external to and separate from the core tally functions, with zero data flow allowed back into the tally function. Any ballot-correction function must create one or more separate totals which are broken down by type. The separate totals must never mix with the core vote counting system, but forever remain independent streams with independent and clearly labeled causes for their existence.
In before someone starts parroting on about blockchain.
To my mind, such as it is, any election software should be open sourced, with all affected parties sitting at the planning table, and every voter given access to the source code. Anything less than full open source or paper and inked finger will never be accepted by me as a legitimate election. Never.