5 ms·
> In an age where updates are increasingly the norm, I wonder if there's legislation needed to hold manufacturers accountable for updates that break otherwise p
by amelius 3y ago
> In an age where updates are increasingly the norm, I wonder if there's legislation needed to hold manufacturers accountable for updates that break otherwise perfectly-functioning hardware?
Maybe there should be a law that says:
1. Upgrades may be performed but never behind the user's back.
2. In particular, the user determines exactly when an upgrade is performed.
3. The user may roll back any update at any time.
4. Any services which the software depends on should be compatible with all versions of the updated software.
EDIT: 5. Security backports should be made available. However, the user should always be in control over whether they are installed. Sometimes working code is more important than 100% secure code. Also this rule will prevent companies from quickly forcing an update and sweeping security breaches under the rug.
- BizarroLand 3y agoI would say that if a manufacturer releases something with software attached then they should also have to release the source code with a time lock so that people would be empowered to dig through the waste bins of electronic history and be able to find/make/learn/do more with it.
- tantalor 3y agoNot gonna happen in a million years
- vlovich123 3y agoSome of those suggestions are things that sound good at first glance but are simply not great ideas. For example, support for downgrades means you a security vulnerability can be reintroduced by a malicious user which may not be desirable. Writing software that’s backwards and forwards compatible across all releases can be extremely expensive to impossible (eg a feature in your application that requires a new OS or you need to use a now removed API when running on older releases). There are difficult technical issues involved and trying to legislate specifics may not be the best idea vs other approaches that improve real freedom (eg you have to release sufficient details to your customers that they can write their own software for your hardware).
- thfuran 3y ago>For example, support for downgrades means you a security vulnerability can be reintroduced by a malicious user which may not be desirable. And there are regulated industries where a software update could be the fulfillment of a recall.
- csdvrx 3y ago> Some of those suggestions are things that sound good at first glance but are simply not great ideas. Actually, yes they are. I'm not a big fan of legislation, but the upgrade crazyness has to stop at some point! > For example, support for downgrades means you a security vulnerability can be reintroduced by a malicious user which may not be desirable What if "I, the user" deem it "desirable"? I'm holding to bios with known vulnerabilities so I can work around "security features" that are "for my own protection" like 1) preventing me from underclocking (to keep the security features of the now-dead SGX) 2) using any M2 WWAN or NVMe that I want It's gone to a point where it's not desirable for me to upgrade, and to prefer the risks that come with an exploit as at least I know my freedom to use my hardware the way I want will not suddenly become limited. Another example: getting root on android with mediatek was considered a "bug" and work a mandatory "upgrade" that prevent users from being able to get root that way. But I want to be root!
- hdhuwgdue2 3y agoRegular bios updates rub me the wrong way. Wife's lappy recently decided to update it of its own volition too. I was livid, but thankfully nothing broke. I hate that OS can do it, but I hate more the fact that bios is clearly less reliable..
- thfuran 3y agoDo you believe that the operator of a deliberately insecure system should be liable if it ends up suborned by a botnet and used to attack someone else's system?
- csdvrx 3y ago> Do you believe that the operator of a deliberately insecure system should be liable Only if said operator signed a contract. No contract=no liability. Here in the US, the Supreme Court has made it clear that law enforcement agencies are not required to provide protection to the citizens cf https://www.nytimes.com/2005/06/28/politics/justices-rule-police-do-not-have-a-constitutional-duty-to-protect.html https://www.nytimes.com/2005/06/28/politics/justices-rule-po... If even the police isn't liable, why should I be liable or have any kind of duty to protect your system? Your system, your problem.
- az226 3y agoWindows 10 forced an updated on my PC and deleted all my personal files. I paid a forensic data firm four digits to get about half my data back.
- at_a_remove 3y agoCould you tell us more about this? Were you keeping your personal files in the usual "Documents" and "Videos" and such laid out by Microsoft? Or somewhere else?
- az226 3y agoYes.
- userbinator 3y agoNot the one you're responding to, but my guess is this: https://news.ycombinator.com/item?id=18189139 https://news.ycombinator.com/item?id=18189139
- 542458 3y ago1 and 2 - this seems incompatible with how 90% of the population uses software, namely they set it and forget it. Having to manually approve and schedule every single update for everything a user touches would be a) a security nightmare, as most things would never get updated ever and b) a UX nightmare, with a million different things asking for updates. 3 - Maintaining a data path forward is tricky enough. Demanding that users be able to downgrade at anytime would be a very tall ask if user data has to survive the downgrade. 4 - This seems outlandishly expensive to do. This effectively reads “nobody can ever deprecate an api on anything”. This also seems to be broadly incompatible with fixing certain security vulnerabilities - would everybody have to maintain TLS 1.1 or plaintext api endpoints for old clients? Would a social media network have to maintain api endpoints that leaked more data than users were comfortable with?
- userbinator 3y agoIt's all an incentive for "don't just churn software, plan well ahead". This also seems to be broadly incompatible with fixing certain security vulnerabilities - would everybody have to maintain TLS 1.1 or plaintext api endpoints for old clients? Or they would forced to produce an update that doesn't do anything other than e.g. upgrade the TLS version --- and has absolutely nothing else.
- stevehawk 3y agoit also skyrockets the barrier to entry for software to a point that no one but the big companies could compete.
- userbinator 3y agoIt raises the barrier enough to stop the lowest-common-denominator forced-obsolescence crap from becoming popular. If an individual can make software that lasts, big companies have no excuse.
- ToucanLoucan 3y ago> 1 and 2 - this seems incompatible with how 90% of the population uses software, namely they set it and forget it. Having to manually approve and schedule every single update for everything a user touches would be a) a security nightmare, as most things would never get updated ever and b) a UX nightmare, with a million different things asking for updates. I don't see how an automatic update setting is incompatible with 2. If a user says "go ahead and install updates as needed" that is the user expressing their desire to receive updates. I also think the phrasing in 1 is a little needlessly aggressive though I believe it comes from a place of frustration. The difference in my mind between saying "this thing updated behind my back" and "this thing updated automatically for me" is whether the user has registered the update as being beneficial or not, and depending on the device, that's a WIDE spectrum. I know my smart outlets update their firmware all the time, and an extremely small handful of times I do notice, because sometimes they end up not reconnecting to the wifi quite right and need to be reconnected. However if they updated and, for example, broke HomeKit support and no longer worked, I'd be angry the next time I tried to use them. > 3 - Maintaining a data path forward is tricky enough. Demanding that users be able to downgrade at anytime would be a very tall ask if user data has to survive the downgrade. I mean, this is just an engineering problem pure and simple. Most of the time, in my experience, graceful downgrade just isn't prioritized because, well, who can even do it for starters? Installing old software oftentimes means you need to do some really intense stuff, like wiping whatever device entirely, so the retention of data is moot. If this was mandated I see no problem with getting it done in my industry. It's simply a matter of making it a priority IMO. > 4 - This seems outlandishly expensive to do. This effectively reads “nobody can ever deprecate an api on anything”. With certain products I can definitely see it being an advantage, and the first place my mind goes to is again, smart home products and appliances, automotive hardware, that sort of thing. Large, expensive items that incorporate software that the user interacts with can be an absolute nightmare when the OEM randomly decides that the way something's worked for years and years for you is now just not an option, or worse still, locks it behind a paywall. And what are your options here? Buy a new car or dishwasher? Or eat shit and pay them $20 a year that they have not earned and are providing no value for? This is why the newest car I have is a 2018 Corvette, because I know all it's software and have access to it, and there's no system that's going to lock my heated seats behind a Chevrolet Premiere+ subscription where I have to give chevy money to permit my car to engage a damn relay for me.
- windows2020 3y agoMy take on this is back when software was distributed on media like CDs, new versions were better. Updates were discrete, marketed and expensive. They had to be good! Continuous updates continue to permeate, including into things that are still surprisingly connected to the internet in the first place. I think that in time, forced updates will cause enough trouble that people will become more conscious of and dislike them. For some, one bad update is all it will take. So, I think it's worth waiting to see if anti-update competitors appear before regulating this.
- dejj 3y agoAmelius’ 5 laws to Asimov’s 3. Make them a bit terser, and maybe “Right to repair” will heave them out of the science fiction tarpit.
- johnchristopher 3y ago> 1. Upgrades may be performed but never behind the user's back. > 2. In particular, the user determines exactly when an upgrade is performed. Haha, at last, yes !! Take that stupid windows XP countdown to reboot !!
- zitterbewegung 3y agoI have a PS3 and Sony removed the ability to load Linux on the device. Basically a class action lawsuit was filed because of the removal . The class action was ruled that they were liable. For number 3 if we allowed for people to roll back any update that can include Teslas where they are doing OTA safety updates so that wouldn’t work out.
- crazygringo 3y agoOh wow. Sony did actually pay, $65 per person. It took 7 years though: https://en.wikipedia.org/wiki/OtherOS https://en.wikipedia.org/wiki/OtherOS