As for the dll files (in my world, we call ‘em ‘libraries’), what you’re saying makes a ton of sense.

FWIW, there was a comment at EW in the past month or so, where someone was asking about ‘pointers’, I think they were expecting to find COPIES of Rove’s old emails, when in fact one ought to look for ‘pointers’ (or ‘library files’ as a first step.

Looking for ‘copies’ seemed futile, and your comment confirms this in spades.
And if you wanted to pull this kind of duplicitous fraud, wouldn’t it be handy to have access to a whole network.

Appreciate your filling in a few blanks; I stay out of the layer you work in ;^}

Lets fix a voting machine.

Today most of the code to run machines is stored in non-volatile flash memory. Flash memory does not lose its information when the power is off, but is too slow to feed instructions to the Processor chip as fast as it uses them so code is normally copied to faster RAM chips (which can’t store anything without power), and executed from there. Since the flash memory is readable and writable from the processor, covering your tracks is simple: at the end of the vote fixing routine, just copy over the routine in the flash with some innocuous code. Ta dah! No record that it was ever in there. Even data checks such as CRC can be fooled or changed, they are intended to catch random accidental errors, not to be tamper proof.

If the pirate code checks something like the date before executing, the machine will pass any accuracy test since the pirate program won’t run before the election, then, on election day, it will run then effectively erase itself. It would also be simple to trigger the erase on some other cue that the machine was being examined, such as a door open switch. Only rigorous code tracing on the source code in the machine itself (NOT the copy the vendor gives you) before the program was run would find this chunk of code. This code needs to be simple to keep the size down.

That is what I think happened in Sarasota, FL in the election that Barbra Harris was SUPPOSED to be in, mysteriously went to the gooper that was in her place. The code was in place when she bought the machines, but was too simple to know that it’s effects were obvious or that Baba was not in the election.

…..

Now, since PCs and servers running windows or Linux is hundreds of thousands of times more complex than a simple voting machine, doing the same thing on a dll file on the hard disk or even the flash boot memory is even easier to hide. No human can step through a megabyte of code, and machine level code is very short and easy to hide, especially when it erases itself. Machine code can be hidden in “data blocks”, which will be copied “as is” into memory and then executed as code somewhere else.

The most hacked code on the planet is Windows, and THAT is what the “bar code readers” that are the “reliable” touch screen replacements run on.

Every bit of this can be coded by one guy and implemented by a single low level person at some point in the system AFTER the code has been checked and certified.

Yes, being from Ohio, the Ohio election has been foundational to my own questions regarding this major network access and the Rove’s number’s comment.

ROT – many in Ohio and Robert Kennedy, Jr. would agree with you…

I’m still checking Rove comments and comparing them with published information on the Ohio election…

Like ROT makes clear…this new information about Verizon almost fits like the missing piece of the puzzle regarding Ohio…

ROTL @ 24 — there have been conversations with people in Congress about the security breach(es); I can’t say much about it, and I don’t know how far along the conversation went, let alone what’s happening as a result. If the entire network is compromised, they already know everything and have likely been working like busy little rodents to undermine any efforts taken to remedy the situation. It’s imperative that we continue to work to seat good, honest people from the grassroots in government, or we will lose it all.

This is rally sickening how MSM keeps it under the rug. The Bush family has a huuge conflict in the spy side of government. They all know full well what data mining gets them…these are private companies, privatly owned with no public disclosure requirements with our information they can use without oversight!

Correct.
Some of us have been supposing that for about two years now, and with the news that the GOP-owned servers were housing the Ohio 2004 Sec of State voting software, it seems highly likely that vote tampering occurred.

Think of it this way: if I’m a legit (programmer/developer), the last thing on earth I’d do is allow myself to even appear suspicious by housing a Sec of State voting operation on a server owned by a political party. Even if everything worked beautifully, and even if all the votes were counted correctly, why would I even take the risk of looking sleazy by putting government business on a GOP-owned server? That’s stupid.

If the Dems had not won the House and Senate in 2006, so that they could hold hearings, I’m not sure we’d have discovered the GOP servers, BTW. (Maybe someone else here has better info, but that’s what I recall.)

There are websites and books that have discussed this issue in depth, and the liklihood that some kind of vote tampering occurred is quite high. However, I have not read the tomes, so can’t provide specific citations. However, you could do some Google searching to find out more.

But from a purely technical point of view:
1. A reputable programmer or business would not permit putting government vote tallies on a server owned by ANY political party.
2. There are ways to write code so that the vote fraud is hard to trace.
3. Wireless communications can also send messages to the software and that can affect how the software functions. This kind of interference would also be hard to trace.

However, there are commenters ’round these parts who work ‘closer to the machine’ than I do. (I don’t write C; they do ;-)) They’re better resources than I am.

They write harder core languages; I only write scripting languages.
But even scripting languages could pull off vote fraud.

And anyone with access to those GOP servers — or with access to the networks — could overwrite logs so that the history of who did what, when, would be harder to trace. Not impossible, but harder.