Source code is the readable programing language that is then compiled to executable code. Executable code is what is located and run on the server and client machines (its not readable)."wiping' out a server or client machine doesnt effect the availability of the source code. The source code (typically proprietary) should be available from Dominion manufacturer - probably need a court order to get it.
Not human readable. Software developer here. We have the ability to reverse de-compile compiled code to a very difficult but human readable version of the code. If we have a machine like I have heard we have. Then we can dump the executables and libraries of that system and show the algorithm. If we have a system that has the cheat settings we can KNOW. However the source code seized is likely already scrubbed of the cheating parts because if I was doing this. I would code the cheat and put it in. Compile then remove it immediately. So the source CODE BASE will not have the cheating part in it but the complied version could.
They can even be sneaky, put the cheat part in the compiler, and every program that is compiled with it has the cheat in it, but it is never shown in the source code.
There is a security practice called reproducible binaries that is meant to help ensure this doesn't happen, but it requires a known good compiler, so you have to trust something, and as we are learning to our sorrow, that isn't all that great an idea when dealing with these people.
This is why you don't trust source code in a matter like this. You disassemble and/or decompile the code on the machines themselves and reverse engineer it. Once you understand the system calls of the OS being used and are familiar with the fundamentals of the CPU architecture, it just takes a little time.
A way to check the source code is you take two machines, one suspect and another a control, compile the code they give you (assuming you can get it with a court Order) and put it on the control. Then you run several stacks of the same ballots through both machines and see if they give the same results. If not, they didn't give you the real source code.
Problem is they claim it's proprietary information and won't be given to anyone. The fact a foreign company "owns our votes" is ludicrous. Either they turn it all over as being part of a federal election, or they maintain it's private info and the courts throw out any and all Dominion vote counts.
It'd take years of lawsuits and they'll send it all overseas which will make it nearly impossible to retrieve from a foreign government like China or Venezuela. Just the fuckery Dominion is doing should be just cause to throw out ALL VOTES where Dominion was used and go from there by sending Trump electors.
The compiled code is all that is in the machine, often called machine code.
Machine code can be understood by people but it requires more than a passing familiarity with the instruction set of the CPU used in the machine in question and it takes a lot of time.
The source code could be compiled it to machine code, then compared with what is actually installed in the machine to see if they are the same. If they are not, then that source code wasn't used in that machine.
Without the source, you could compare the machine code between two machines to see if they are different.
A simple check is: Are they the same file size? If not, they were not created from the same source. If they are the same size, you can do a character (byte) by character comparison to see if they are the same.
The executable 'machine readable' code is on the machines. What you want is the source code that is maintained separately by the manufacturer. Typically you maintain configuration control of the source code by version. So its also important to know the exact version that is running on the machines so you get the right source code from dominion. No one puts source code on the operational machines/computers.
Source code is just text. You can only read it or compile it to make an executable program. Production servers run programs which actually do something. Source code is just plain text. 100% sure regular Dominion machines don’t have any source code. They simply have the executable already compiled binary files, which are not human readable.
Source code is the readable programing language that is then compiled to executable code. Executable code is what is located and run on the server and client machines (its not readable)."wiping' out a server or client machine doesnt effect the availability of the source code. The source code (typically proprietary) should be available from Dominion manufacturer - probably need a court order to get it.
Not human readable. Software developer here. We have the ability to reverse de-compile compiled code to a very difficult but human readable version of the code. If we have a machine like I have heard we have. Then we can dump the executables and libraries of that system and show the algorithm. If we have a system that has the cheat settings we can KNOW. However the source code seized is likely already scrubbed of the cheating parts because if I was doing this. I would code the cheat and put it in. Compile then remove it immediately. So the source CODE BASE will not have the cheating part in it but the complied version could.
They can even be sneaky, put the cheat part in the compiler, and every program that is compiled with it has the cheat in it, but it is never shown in the source code.
There is a security practice called reproducible binaries that is meant to help ensure this doesn't happen, but it requires a known good compiler, so you have to trust something, and as we are learning to our sorrow, that isn't all that great an idea when dealing with these people.
Yeah, I didn't think of that but your correct.
Its a little esoteric, most coders don't even think about these things.
He's correct. One method to do this is called dependency injection.
This is why you don't trust source code in a matter like this. You disassemble and/or decompile the code on the machines themselves and reverse engineer it. Once you understand the system calls of the OS being used and are familiar with the fundamentals of the CPU architecture, it just takes a little time.
A way to check the source code is you take two machines, one suspect and another a control, compile the code they give you (assuming you can get it with a court Order) and put it on the control. Then you run several stacks of the same ballots through both machines and see if they give the same results. If not, they didn't give you the real source code.
Problem is they claim it's proprietary information and won't be given to anyone. The fact a foreign company "owns our votes" is ludicrous. Either they turn it all over as being part of a federal election, or they maintain it's private info and the courts throw out any and all Dominion vote counts.
It'd take years of lawsuits and they'll send it all overseas which will make it nearly impossible to retrieve from a foreign government like China or Venezuela. Just the fuckery Dominion is doing should be just cause to throw out ALL VOTES where Dominion was used and go from there by sending Trump electors.
Isn't the code also in Dominion machines??? They want to get rid of the machines now!
The compiled code is all that is in the machine, often called machine code.
Machine code can be understood by people but it requires more than a passing familiarity with the instruction set of the CPU used in the machine in question and it takes a lot of time.
The source code could be compiled it to machine code, then compared with what is actually installed in the machine to see if they are the same. If they are not, then that source code wasn't used in that machine.
Without the source, you could compare the machine code between two machines to see if they are different.
A simple check is: Are they the same file size? If not, they were not created from the same source. If they are the same size, you can do a character (byte) by character comparison to see if they are the same.
The executable 'machine readable' code is on the machines. What you want is the source code that is maintained separately by the manufacturer. Typically you maintain configuration control of the source code by version. So its also important to know the exact version that is running on the machines so you get the right source code from dominion. No one puts source code on the operational machines/computers.
Source code is just text. You can only read it or compile it to make an executable program. Production servers run programs which actually do something. Source code is just plain text. 100% sure regular Dominion machines don’t have any source code. They simply have the executable already compiled binary files, which are not human readable.