Sat Aug 14 02:08:46 +0000 2021

_{[tweet] [link]}
I have a theory for why that may have seemed to be the case...per the CO Trusted Build guidelines and the Dominion manual linked below, it seems like the upgrade process involves restoring an image created with Acronis

https://votingsystems.cdn.sos.ca.gov/vendors/dominion/ds510-use-proc-jan.pdf https://www.sos.state.co.us/pubs/elections/VotingSystems/files/trustedBuildProcedures.pdf

_{[tweet] [link]}
So what I think happened - but could be wrong - is that they created the trusted build on a machine elsewhere, and then restored that image to the Mesa Co. EMS server...which, really, restoring a known good image is more secure than just updating software packages

_{[tweet] [link]}
Suppose malware had been on the EMS server prior to the upgrade, if they just upgraded the packages, that malware would still be there. Restoring a known good image mitigates that.

Also, Ron's "whistleblower" video showed a disk actively being restored by Acronis

_{[tweet] [link]}
The manual linked above also specifies backups should be made prior after the election. So yes, the "after" image did not have the log, because they restored a fresh image that had been created in a safe environment, and per CO regulations,should have also been approved by a VSTL

_{[tweet] [link]}
But, if clerks like Tina Peters had been doing their job, they should have followed the guidelines specified by Dominion that state that backups of the election results and election project should have been made.