as much as I would love that personally, the software is an asset and bankruptcy means they have to try and liquidate all assets in order to cover their liabilities. besides, bankruptcy doesn't always mean the company and all services disappear.
imo a reasonable middle ground is to prevent companies from locking down access to the vehicle's computers. owners should be able to root and self-manage the software, even if that software has to be painstakingly reverse engineered.
ofc the safety critical systems make that trickier but still.
Comments
I'd go even further, if the company goes bankrupt, the company should be required by law to open source the code.
The argument that the code may contain third-party licensed code that can't be open sourced is the usual retort that comes next.
I'm with you, though. This is a place where consumer protection needs to be bolstered.
Also, the build tools, whatever's necessary to sign/flash firmware, and they must demonstrate repeatable builds.
as much as I would love that personally, the software is an asset and bankruptcy means they have to try and liquidate all assets in order to cover their liabilities. besides, bankruptcy doesn't always mean the company and all services disappear.
imo a reasonable middle ground is to prevent companies from locking down access to the vehicle's computers. owners should be able to root and self-manage the software, even if that software has to be painstakingly reverse engineered.
ofc the safety critical systems make that trickier but still.