A series of tweets by an IT specialist destroy almost any confidence in a protected control environment surrounding the Dominion voting machines.
Numerous heroes around the US and around the globe are pitching in to offer their expertise to save the nation and our individual freedoms. No American in good conscience wants a stolen election marred with fraud to stand.
One IT specialist by the name of [email protected] has unloaded a series of tweets identifying major control weaknesses within the Dominion voting machine environment.
Below are a series of tweets from Ron regarding the weak or nonexistent controls within the Dominion voting machines and applications. These observations are frightening.
TRENDING: BOOM! TRUMP TWEETS: REPORT: DOMINION DELETED 2.7 MILLION TRUMP VOTES NATIONWIDE. DATA ANALYSIS FINDS 221,000 PENNSYLVANIA VOTES SWITCHED FROM PRESIDENT TRUMP TO BIDEN
Ron first explains that he located a Dominion vendor user guide:
I found a vendor user guide with images showing how the Dominion 5.5 central tabulating software works and transmits results from your ballot to the county. Do you trust your election workers to copy and paste files and folders to USB without tampering? cms5.revize.com/revize/calhoun
Ron then asks:
Are your election workers being monitored during this process? If so, who is watching them take data from the tabulator machine, copying it to a flash drive, and delivering it to the county office? Is a proper chain of custody maintained?
Are your election workers being monitored during this process?
If so, who is watching them take data from the tabulator machine, copying it to a flash drive, and delivering it to the county office?
Is a proper chain of custody maintained?— Ron (@CodeMonkeyZ) November 12, 2020
Next Ron notes:
Pennsylvania Department of State requested a function from Dominion Voting Software to allow local “Operators” with access to “totally blank ballots” to examine, RE-MARK IF NEEDED and allowed, and then re-scan into the tabulator. dos.pa.gov/VotingElection
He again asks about controls surrounding the system functionality – are the election workers being monitored?:
Are your election workers being monitored during this process? If so, who is watching them take data from the tabulator machine, copying it to a flash drive, and delivering it to the county office? Is a proper chain of custody maintained?
Are your election workers being monitored during this process? If so, who is watching them take data from the tabulator machine, copying it to a flash drive, and delivering it to the county office? Is a proper chain of custody maintained?
Has Pennsylvania ever sent blank ballots to constituents?
If yes, what eventually happened to those blank ballots?— Ron (@CodeMonkeyZ) November 12, 2020
Pennsylvania voters with blank ballots are being requested to send in their ballots to the RNC. The RNC likely believes these ballots may be a problem or may be related to fraud:
Ballots are 100% interlinked with the voting software. Sending a blank ballot allows the software to tabulate votes differently from a ballot that is correctly populated.
Whether these blank ballots were used for fraud is an exercise for investigators to prove. https://t.co/rAsvw2X2vW
— Ron (@CodeMonkeyZ) November 12, 2020
Ron claims he could find any fraud within these machines and the process surrounding them if given the opportunity to review – he also has reached out to Rudy Giuliani:
If I had forensic access to the live configuration data, logs, settings, and intranet setup of the Dominion voting system used in the districts reporting anomalies, im confident I could quickly and conclusively blow the lid off digital election fraud if it had actually occurred.
— Ron (@CodeMonkeyZ) November 12, 2020
Ron notes that there are absurd settings within the software which allows a local IT guy to totally influence an election:
The absurd amount of “settings” on the Dominion Voting Software is off-the-charts.
If I was a local IT guy, I could probably setup the voting machine to give myself an elected position without ever being on any ballot or running any campaign.
— Ron (@CodeMonkeyZ) November 12, 2020
Who is watching the local IT guys?
Where are our checks and balances for the local IT guy? Who is auditing his actions? Where are the logs? Which settings did he enable? Did he change settings? When?
— Ron (@CodeMonkeyZ) November 12, 2020
Another nine tweets from Ron were unrolled – they are frightening:
What we have learned so far from reading the Dominion Voting System manual:
1. Votes can theoretically be ignored for individuals if a straight ticket vote is selected. This setting could very welI enable “Repubiican”-style typo fraud. Many complex rules decide how the “straight ticket” option works.
2. Network Security is very weak since all software access keys use the same cryptographic pair. This gives plausible deniability to whoever potentially decides to mess around with voting settings. It cant be proven who changed a setting since everybody has the same key
3. Digital certificates are not protected by password, and Dominion user manual explicitly says not to enter a password. This enables potential for bad actors to MITM attack data traveling over network between precinct tabulator and central tabulator.
4. Cryptic “split rotation” function that features the ability to “force a maximum deviation”. There is no definition of a “split rotation”, so we cannot know what “force a maximum deviation” means in this instance.
5. Local IT guys have ultimate power to clandestinely change settings, thus having the ability to potentially alter an entire election. There are no checks and balances or observers of the local IT guy when he accesses machine debug and admin settings. Its unclear if logs exist.
6. Dominion is a black box with votes ultimately tabulated in a central server system. Who has access to the central server and where is the manual and security reviews of that server software?
7. Settings could theoretically have been changed during evening downtime on first night of voting. Much easier to change settings on hundreds of machines than to forge thousands of ballots. A couple of people could have done it quickly.
8. State of Pennsylvania requested semantic changes to the Dominion voting software, possibly to aid in their lawfare efforts. The word “Cast” became “Print”, obfuscating the moment when your vote becomes officially cast. For what reason is currently unknown.
9. There is an option to force the vote scanner to “overrun” a preset amount of ballots EVERY time anybody pauses the scan mid-batch. “Overrun” is undefined. Potential for abuse is high with this function, which was added shortly after 2018 mid-term elections.
Ron asks the ultimate question with the software used in the Dominion voting machines:
Too bad we dont have the dominion source code to review. These types of things should be open source so everybody can poke through it.
Why do we have black box elections?— Ron (@CodeMonkeyZ) November 11, 2020
Again, Ron states the local IT guy who services Dominion machines has the power to decide elections:
After reviewing the Dominion Voting System user manual, it seems the local IT guy who services the machines is theoretically the ultimate political gatekeeper.
He has absolute power to decide elections.— Ron (@CodeMonkeyZ) November 11, 2020
Since everyone supposedly has the same USB key, if any participant loses that key the integrity of the election is lost:
So this means that any participant who loses their USB key which stores the encryption key has then destroyed the integrity of the election in that district.
Someone mind telling me what was stolen in Philly again?
— Ron (@CodeMonkeyZ) November 11, 2020
USB drives were reported stolen in Philly before the election:
Remember the USB drives stolen in Philly? Those USB drives were admin access devices to enter the configuration and debug screens of the voting machines. With those stolen drives, someone could potentially change, purge, or inject ballots with impunity.https://t.co/Z06yrsWEwO
— Ron (@CodeMonkeyZ) November 11, 2020
