I had the same thought about dlls. Most people do not understand the layered nature of computer programs these days.
Even if people perform a complete walkthrough of the app's code they always omit the lower layers but those can be corrupted as well. That still leaves the device drivers unmonitored and the operating system itself.
I have written programs in the past that would remove a part of themselves after execution making investigations difficult. You could write a perfect program that opted to be more devious if, say, a USB drive with a specific volume name were inserted. The USB would effectively be a key to switch on the data corruption code. Or you might use data from disk sectors marked as bad.
The possibilities are endless and if someone can make a quick buck or billion out of it is it going to happen? You bet your life it is.
Why people trust computers for voting still defies belief.
Aside - For the non computer experts:
If we compare a computer program to a company, a dll is a bit like having a reprographics department that will do all your photocopying for you. While you might audit the company's finances you will probably never check whether that department is making exact copies or whether it is modifying the output. Imagine if you ordered a thousand copies of something but they had changed a QR code somewhere. Would you ever notice?
30 years ago a single byte of data had to go down through 7 layers of software and hardware before it hit the Ethernet cable as an electrical signal, and then back up through 7 layers on the other side. I doubt it's any less today. And the developers coming into industry today can't seem to write a basic program with a simple and elegant piece of code. Don't get me wrong, they are smart and know a lot more than me about manipulating threads, managing collections, etc. But they all seem to write the most incoherent and complex code that requires days of debug just to do something I would consider relatively simple.
I can't imagine how long it would take to scour the code produced by a team of developers with a few of them supporting the corruption.
The DLLs are the MOST IMPORTANT FUNCTION of Programs to function correctly, especially offloading codes that can do tasks...IF there was an insertion of code that the dll executed, it will be there...BUT, it depends on HOW far the "code" is in the dll(s)!!!!!!...
OK, but, I have just looked at the dlls on my PC and I have 32 copies of one dll. How would we know which one ran at the time? Might the dll that did run have been replaced after it was used?
AND YOU HAVE DONE THE SAME THING I DID!!!! Duplicate DLLs in places you would not expect them... also, when I program, I put all the dlls in one spot and secure them...
NOTE: We don't know how many dlls are in the voting system, but I guarantee you, if they get the right programmers in there, they will find exactly how it was done. However, if those dlls were written in C++, then it is game over!!!! AND I am pretty sure they were due to the amount of chicannary that went on when these systems were being built!!!!
I had the same thought about dlls. Most people do not understand the layered nature of computer programs these days.
Even if people perform a complete walkthrough of the app's code they always omit the lower layers but those can be corrupted as well. That still leaves the device drivers unmonitored and the operating system itself.
I have written programs in the past that would remove a part of themselves after execution making investigations difficult. You could write a perfect program that opted to be more devious if, say, a USB drive with a specific volume name were inserted. The USB would effectively be a key to switch on the data corruption code. Or you might use data from disk sectors marked as bad.
The possibilities are endless and if someone can make a quick buck or billion out of it is it going to happen? You bet your life it is.
Why people trust computers for voting still defies belief.
Aside - For the non computer experts: If we compare a computer program to a company, a dll is a bit like having a reprographics department that will do all your photocopying for you. While you might audit the company's finances you will probably never check whether that department is making exact copies or whether it is modifying the output. Imagine if you ordered a thousand copies of something but they had changed a QR code somewhere. Would you ever notice?
30 years ago a single byte of data had to go down through 7 layers of software and hardware before it hit the Ethernet cable as an electrical signal, and then back up through 7 layers on the other side. I doubt it's any less today. And the developers coming into industry today can't seem to write a basic program with a simple and elegant piece of code. Don't get me wrong, they are smart and know a lot more than me about manipulating threads, managing collections, etc. But they all seem to write the most incoherent and complex code that requires days of debug just to do something I would consider relatively simple.
I can't imagine how long it would take to scour the code produced by a team of developers with a few of them supporting the corruption.
The DLLs are the MOST IMPORTANT FUNCTION of Programs to function correctly, especially offloading codes that can do tasks...IF there was an insertion of code that the dll executed, it will be there...BUT, it depends on HOW far the "code" is in the dll(s)!!!!!!...
OK, but, I have just looked at the dlls on my PC and I have 32 copies of one dll. How would we know which one ran at the time? Might the dll that did run have been replaced after it was used?
AND YOU HAVE DONE THE SAME THING I DID!!!! Duplicate DLLs in places you would not expect them... also, when I program, I put all the dlls in one spot and secure them...
NOTE: We don't know how many dlls are in the voting system, but I guarantee you, if they get the right programmers in there, they will find exactly how it was done. However, if those dlls were written in C++, then it is game over!!!! AND I am pretty sure they were due to the amount of chicannary that went on when these systems were being built!!!!