Hacker News new | ask | show | jobs
by watt 1732 days ago
Stronger than that. When releasing the gadget, require that the firmware source build tree is put in escrow. After 5 years it is opened to enable ongoing maintenance.

The initial release of gadget is released with firmware build by the escrow build process. This will ensure the company actually provides tree that builds the real thing.

1 comments

Good idea, better than classic escrow: With a classic escrow, your customers are incentivized to make you go bankrupt, so that they recover the source code and eat your benefits.

But that doesn’t solve the vulnerabilities and the need to have 0-day updates.