Anonymous ID: 1e20bd Aug. 14, 2021, 6:16 p.m. No.14354559   🗄️.is 🔗kun   >>4565 >>4592 >>4729 >>4749 >>4761 >>4878 >>4888 >>5063

>>14354359

ty, baker

 

Anons.

Lowest-ranking anon here. I don't know if anybody else is working on the disk images from CM, but I figured I'd post my progress report.

Almost all of my seeds have completed, but one. The single non-POSIX machine I'm using won't complete. Figures. I'm going to kill it, lest it poison others. But I see fewer than six (6) peers, and not-quite one-hundred (100) seeds on all of my remaining seedboxen. I guess most of the people who intent to DL the file have done so, but I will keep seeds up for as long as I am able.

I've scanned the packages using ClamWin and Avira, without finding anything suspicious. I've also validated the sha256 sums on all the torrented ZIP files, as well as the E01 files contained therein. Everything checks out.

And, following-along like the lowest-ranking-anon I am, I spun-up a Debian VM and worked through the document dropped by a fren: www . andreafortuna . org/2018/04/11/how-to-mount-an-ewf-image-file-e01-on-linux/

I have the images mounted, and can see their contents within the BASH commandline, but I'm still working to setup SAMBA to easily view them from a Winblows machine. But I can already tell that there is some fuckery afoot or maybe I'm making a mistake.

The two images do not appear to be partitioned the same way, and I'm not sure how to explain what I'm seeing.

The zeroeth image is for an MBR disk, with a Windows installation on it. And the second image is a GPT disk, with another Windows installation on it. Odd. The were probably using a specific disk image for the election, and then the wiped it and reloaded it with the default GPT image (with secure boot re-enabled) and default BIOS settings restored.

They probably did a wipe-and-reload on all the machines, with help from Dominion personnel.

Absolute proof, assuming these files are real. How do we validate the Dominion installation contained within them?

Both of them have the "Dominion Voting Systems" software within "C:\Progra~1", but they have different user accounts. And moar EMS user accounts on the zeroeth image than the second.

I intent to setup an environment where I can show people the differences between the two disk images, but demonstrating the provenance of the files will be my hurdle.

Am I just sputid sic? How do we prove that these came from the Dominion server in Colorado?

I think the key is going to be analyzing the contents of the SQL databases, or something. Could really use some help from a higher-ranking anon….

ty, GEOTUS, VP Mike Lindell, Iron Eagle, Red Team, and frens.

We will win.

Anonymous ID: 1e20bd Aug. 14, 2021, 7 p.m. No.14354911   🗄️.is 🔗kun   >>4980

>>14354890

> Clicknigger strikes again

>>14354878

ty, anon

I'm not even sure where to begin.

But I'm not even sure where to begin.

What information will exist on these images that would not be available outside of the election system?

What makes these databases unique, as opposed to something I threw together as a hoax.

How do we demonstrate that the data within are not fraudulent?

Anonymous ID: 1e20bd Aug. 14, 2021, 7:14 p.m. No.14355012   🗄️.is 🔗kun   >>5082

>>14354980

> The de-hardening and deleted dbs and logs are the info that needed to get out.

Yes, but have we even demonstrated that? Without chain-of-custody, do we know for certain the the disk images even came from Colorado?

How do we prove that the dehardening and deletion occurred on election machines and not lab/test machines?