You're really that blind, aren't you?

Require registration (don't they do this with cars?) and notify the customer via snail mail or e-mail (user's choice) when a bug is found so that they can fix it. Give them a manual that's worth a damn and the burden is on the user to actually read it to limit your liability to bugs instead of stupid user tricks.

If your product is completely a piece of crap (M$ WinME anyone?) and causes data/money loss (all data loss is a loss of money, it takes time to enter data and time=money) then they should be vulnerable for that. I don't know how many people lost data because of WinNT SP2. How about when M$ changed to NTFS5 with a SP. What do you do when you can't access your data because of the change to your FS? There are lots of other products (most of them with "Crash" in their names, like Crashguard) that cause crashes and potential data loss, shouldn't they be prosecuted for costing someone money because it was used as instructed and lost money as a result?

If your product causes data loss, you need to recall it. Force registration (and don't spam the person with marketing crap because they did so) and use it to help the user instead of using it to line your pockets.

Responsibility shouldn't be avoided because you wrote a slick (and BTW, unenforceable) license agreement that you force people to agree to before they can see it.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/47/9674#9674