I understand that most software creators want to cover their butts (and save on the expense of support) by detaching themselves from responsibility. Hence the "use at your own risk" statements. But backdoors? If I were a software creator...no, if I were the person in charge of the business decisions the software creators have to live by, there's NO way I'd incorporate such a process into my software without making it UNDENIABLY clear to the user that it's for their own good.
People don't like sneaky software and just one product that gives you a black eye can ruin your ability to sell products in the future. There's always competition and your competitors would just LOVE for you to piss off your users.
Anyone got any examples of license agreements where the user has to agree to an open back door? I'm up for being corrected.:)
Slashdot Mirror
I understand that most software creators want to cover their butts (and save on the expense of support) by detaching themselves from responsibility. Hence the "use at your own risk" statements. But backdoors? If I were a software creator...no, if I were the person in charge of the business decisions the software creators have to live by, there's NO way I'd incorporate such a process into my software without making it UNDENIABLY clear to the user that it's for their own good.
People don't like sneaky software and just one product that gives you a black eye can ruin your ability to sell products in the future. There's always competition and your competitors would just LOVE for you to piss off your users.
Anyone got any examples of license agreements where the user has to agree to an open back door? I'm up for being corrected. :)
bTJOD
~-- Yet another posting forum : nerd center --~