REMOVE BATTERIES SOON, FBI?:

Rebooting after re-powering Dominion terminals up, after 40 votes or so, and after time moves forward a day after shutdown from its internal clock, might re-flashes themselves to hide blatant Nov 3 fraud logic evidence. (assumed). The FLASH chips onboard on all cpu components (firmware) needs to be de-soldered , with no power given to the circuit boards, in case the logic to reflash is duplicated hidden in the firmware flash modules themselves! Battery power might even be enough to reflash and hide a small hack.

Rough thoughts... excuse typos...

Rebooting hides the core evidence of one attack vector

Paper oriented dominions are simpler : merely opening the election seal and hand counting machines that entomb paper ballots, will show massive miscounts of Trump. Sadly, official seals were removed by mysterious unknown parties in some areas of USA , like Gwinnett County, Georgia (proven) : https://tennesseestar.com/2020/11/10/georgia-whistleblower-officials-used-ballot-machines-missing-security-seals-in-gwinnett-county/

This prevents ability to catch a Dominion in the act of swapping Trump votes for Biden by looking at papers inside.

Downballot Letter I" "media profile?

Letter I" trick caught using math by Dr. Shiva, cost Trump about 100,000 votes per state who used "downballot" checkbox : https://files.catbox.moe/dp54kf.jpeg

"Letter I" in republican spelled as Uppercase "I" trick, for 17% of downballot checkbox people (most do not use downballot box, not even dems)!!!

The media profile might even rewrite itself, hiding the Letter I trick, making it magically start working properly.

But internal or external hacking, unrelated to Letter I, was seen in Michigans reddest county, when it became one of the bluest counties due to hacking setting fuckup (it did not keep tally within 4%) :

https://thefederalist.com/2020/11/06/software-glitch-in-michigan-county-tallied-6000-republican-votes-as-democrat/

Georgia's machines that failed , close to election, got a mysterious new firmware 2 days before election.

Android operating system

The source code shows that Android operating system is used internally in recent years. Android and that type of CPU pair is too powerhungry in hibernation nap mode to reflash anything, so the reflash cannot be done off dormant battery from main android cpu, but a hidden microcontroller near the flash could drive a modifier and even miraculously use a "collision" hash to make both firmware versions depict the same "signature". A hidden microcontroller would still need to use a huge amount of amp hours to drive flash mod of entire two copies of 1 megabyte flash. But a clever hack will modify a tail end of about 100 kilobytes, plus the MD5 hash sweetener to form a crypto collision match.

3rd area of a flash image :

The third area of flash, the checksum watch-dog that chooses backup copy at boot, if main firmware has a bad checksum, need not be reflashed, but it too, that secret little part, could have the main exploit in it and need analysis by Trump, and hiding by bad actors. It might even hold the logic to HIDE THE EVIDENCE after 24 hours reboot. 95% of all computers use more than one backup copy of firmware in flash. Mainly because Flash RAM can only be rewritten 50,000 times before being dead. (30,000 on average)

The tiny stub of firmware in the flash needs to be forensically preserved very soon, without letting it cover itself up. The source code to tiny 3rd flash partition will NOT be reflected in the 473,991 lines of source code of ICP2 firmware.

Studying the code for firmware reloading via USB dongles, will only reveal another means, but no evidence.

Geogia got mysterious new unvetted firmware in two Counties from Dominion at last minute!!!:

Politico disinfo : Election Day glitch in Georgia counties still unexplained:

https://www.politico.com/news/2020/11/04/georgia-election-machine-glitch-434065

The reason I used leftist Politico link, is because it clearly states that the firmware updates were HIDDEN from the device logs and used a covert way of being updated that avoids writing to system log of Dominion. Specifically, this unaltered exact verbatim quote from that link:

But log files for the devices — electronic poll books that poll workers use to sign in voters at precincts — show that no such update occurred to the devices the night before Election Day, Ridley said in a statement to POLITICO on Thursday. However, she said she stands by her previous statements last week that a representative for the election technology vendor, Dominion Voting Systems, told her office that it had uploaded some kind of update the night before the election and that this had created the glitch.

NSA type intercepts of cell phones, internet, etc, will need to be used to find the real bad actors, but desoldering flash chips before applying power would help , if the battery clock battery is not used to drive the re-flash based off a timer tied to count odometer.

FBI should rip out all batteries pronto, and desolder Flash chips pronto.

MY REVELATIONS (not so secret)

Source code defects in "Dominion Democracy Suite Voting System" I pronounce include :

• The system allows the user to select the size of RSA keys, including 1024 bit, laughable in 2020.

• SHA-1 in RSA signature generation !!!! :

  https://threatpost.com/exploit-fully-breaks-sha-1/151697/

SHA-1 is a Shambles:

(PDF) https://eprint.iacr.org/2020/014.pdf

• Use of MD5 : MD5 is only good for corruption detection, NOT security! NSA banned it in 2001. FIPS 140-2 from 2001 says to use approved secure hashes. People have published "collisions" of any MD5, if bytestream can be stretched.

• Weak crackable AES 128 bits used!!! Should be AES 256, but the code silently drops it to AES 128 in undocumented fashion.

• Debugging harness code hidden in production firmware builds allows anyone with debugger harness access to RAM space. (proven).

• Hard coded encryption keys hidden in source code (yes really)

• Sensitive keys are stored on disk unencrypted and a external device can trivially read these critical crypto keys.

• Hard coded encryption keys hidden in source code of the master vote tabulator for the precincts (yes really)

• Random number and entropy routine to make live challenge-response keys lacks enough entropy and thus makes VERY CRACKABLE transmission keys.

Note that the diversity hire chin-tapping retard code reviewers hired by State of California to find those exploits found NONE and put NONE in their August 2019 security overview report shown here : (PDF) https://votingsystems.cdn.sos.ca.gov/vendors/dominion/dvs510software-report.pdf

That corrupt Democrat-loving code review company is called "Gaming Laboratories International, LLC" A casino machine review company hired to look for gambling exploits in random number generators and nothing else, it seems.

https://gaminglabs.com/ found NOTHING I mentioned in the ICP2 firmware/hardware 473,991 lines of source code. They found NO PROBLEMS of democrat inserted cryto weakneses I listed! Bwah hah hah hah hah! Neither did CodeMonkey or his pals yet.

Are we living in CLOWN WORLD, when women and diversity skin retards are hired for penetration source code analysis?

All the exploitable weaknesses above could be used to rig an election on a machine, within a machine, though on vote night EXTERNAL COUNT manipulation via Q-Snatch NAS and compromised MS Windows via Europe was more visible,

Leftist Democrat Soros shills and Tel Aviv Jews on voat will downvote this.

JEW SHILL DOWNVOTES of my priceless truths!

FBI should rip out all batteries pronto, and desolder Flash chips pronto.