Hacker News new | past | comments | ask | show | jobs | submit login

I think this is what I'd like to see...

The manufacturer of the device is responsible for security updates forever. If at any time a security flaw is discovered in the device, they have two options:

1. Develop and deploy a fix at their own expense, and make it freely available to all owners of the device.

2. Publicly release all source code and documentation necessary for any third party to independently develop and deploy a fix.

This way, any company which still cares about their customers, devices, patents, copyrights, etc which are involved will pay the expense of fixing the problem, as the cost of keeping that which they value. And any company which does NOT care about those things can simply walk away from it all at no cost to themselves.

So, as a dude in your workshop, after n-years have passed and you feel the responsibility is too onerous, you opt for #2 and wash your hands of the mess.

As an interesting side-effect, this opens up a business opportunity for source and documentation escrow services. Because if you've somehow managed to lose some or all of your source and documentation, you've also lost the ability to choose door #2.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: