"With those stolen USB drives, someone could potentially change, purge, or inject ballots with impunity." |
This was one of his first findings (emphasis mine):
"1) There is a setting to throw out votes for specific individual contests if you vote for a whole party.
"With the Party Preference contest, the voter selects their preferred party, and any contests which do not belong to the same Elector Group are ignored when the ballot is cast."
A bad operator could theoretically setup the ballot to put a specific candidate into a party that is not his official party. If you select his party and vote for the party, the individual candidate won't get a vote.
Scenario:
Republican -> Trump
RepubIican -> Trump
*LOOK CLOSELY*
In the second scenario, if you voted for the Republican party, Trump would NOT receive a vote because he was registered to the "Repubiican" party.
This might explain why Trump performed poorly in strong Republican districts. In the second scenario, if the voter just voted straight-ticket, then a Trump vote would be ignored.
I'm NOT saying this is what happened, but it is a supported feature of the voting software."
In light of this discovery, it may be significant that on October 3, 2020, President Trump tweeted:
"Going welI, I think! Thank you to all. LOVE!!!"
"Going welI, I think!" Well spelled with lower case l, Upper Case I. |
Online researchers at the time picked up on President Trump's spelling 'mistake' and wondered if it could have any significance, or if it could be some sort of message.
Here's a later thread from Ron summarizing most of his conclusions so far:
"What we have learned so far from reading the Dominion Voting System manual (emphasis mine):
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 can't 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.
The local IT guy 'has absolute power to decide elections.' |
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.
More to come later.
Many people have sent me (completely publicly available) Dominion security audits, documents, manuals, and state contracts. Have a lot of reading to do.
If there are any potential election fraud settings hiding in plain sight, I will do my best to find it."
- - - - - - - - - -
Chanel Rion of OANN has reached out to Ron, so he'll be talking with her about Dominion later today.
If you want to stay up-to-date with CodeMonkeyZ's findings then he's definitely worth a follow on twitter:
@CodeMonkeyZ
No comments:
Post a Comment