Now, I'm not personally interested in reverse-engineering arbitrary binaries to audit them for security virtues or vulnerabilities...
But, with respect to compilers, ancient compilers, ancient compilers which exist in binary form only (no source code!), ancient compilers which exist in binary form only, where the company and/or individuals that once produced them -- have long since went out of business, ancient compilers that (because they are so old!) -- are no longer viable products in the markets of today, that is, they could no longer be sold for any profit...
Well, for those ancient, binary-only compilers -- I think tools like the one you've outlined above -- would be excellent, excellent research tools(!) for future computer historians and academics, to morally/ethically/legally/lawfully decompile those old binaries -- for greater understanding(s) of what they were, how they worked, how they were programmed, and how the original authors thought about compiling code!
Anyway, great link!
This was an interesting read. Specially the technical errors in Ramslands (ASOG) report was eye opening.
https://www.usenix.org/conference/usenixsecurity22/presentat...
The tl;dr for Antrim County seems to be that the county spotted an error in their ballot format a few weeks before the election and got their ballot vendor to generate new ballots, but failed to consistently update all their equipment, so in a bunch of precincts all the Presidential votes got shifted by one candidate. Real votes for Biden were discarded, votes for Trump were recorded for Biden, and votes for Libertarian candidate Jo Jorgenson were recorded for Trump. A small remainder of incorrect votes somehow (I'm not reading carefully, but the paper has it exactly) had to do with miscoding of straight-ticket voting options.
Interestingly, a single discrepancy that apparently Halderman found on his own may have altered the outcome of a ballot initiative in Central Lake, MI, which was decided by one vote.
