Do You Write Backdoors?

quaxzarron asks: "I had a recent experience where one of our group of programmers wrote backdoors on some web applications we were developing, so that he could gain access to the main hosting server when the application went live. This got me thinking about how we are dependent on the integrity of the coders for the integrity of our applications. Yet in this case a more than casual glance would allow us to identify potentially malicious code. How does this work when the clients are companies who can't perform such checks - either because they don't know how, or because the code is too large or too complex? How often do companies developing code officially sanction backdoors...even if means calling them 'security features'? How often has the Slashdot crowd put a backdoor in the code they were developing either officially or otherwise? How sustainable is the 'trust' between the developer and the client?"

Comments

Why would you care?

[Ars-Fartsica]

Its just an extra insurance policy for when some moron that I worked for 6 years ago does something stupid.

And as a former employee, you give a shit why???

Re:Backdoors in the brain

[valkraider]

to labotomize the developer or somehow wipe his/her memory.

Otherwise known as MCSE.