Question: What prevents a programmer from installing a back door into their program and then editing it out of the source code after they compile it?
Open Source: Hacker's Backdoor
Started by ki4jgt, Oct 20 2010 10:23 AM
5 replies to this topic
#1
Posted 20 October 2010 - 10:23 AM
|
|
|
#2
Posted 20 October 2010 - 04:36 PM
Absolutely nothing, other than the ability of other people to compile it themselves.
#3
Posted 20 October 2010 - 05:00 PM
True, but what do most people do? They download it directly from the site. So, have there ever been any cases of this, or has anyone ever been caught?
#4
Posted 20 October 2010 - 05:25 PM
This is not so much about "open source", anybody can claim the compiled executable is the source that is showed, but I only compile from source, package managers only compile from source, because there is a very diverse amount of computer architectures and operating systems, running a compiled executable compiled on system "A" does not mean that it will run relatively bug free on yours, all the better to compile it from source.
Be sure to read the updated FAQ! || Health is achieved through the same 10,000 steps.
If a suggested code/method fails, informing us is less important than telling us why or what errors occurred.
If a suggested code/method fails, informing us is less important than telling us why or what errors occurred.
#5
Posted 21 October 2010 - 04:22 AM
Put a different way, if given the source code to a project, how many people just run make, make install versus actually inspecting the code? It's an issue, but it beats the heck out of some of the alternatives, like downloading freeware with malware bundled in, or having things like Windows calling home periodically to determine if it thinks you're still legal.
#6
Posted 21 October 2010 - 07:36 AM
That one's true. I don't know, It just popped into my head the other day. "hey, what if these developers made programs that were claimed to be safe, but weren't 100%"


Sign In
Create Account


Back to top









