this post was submitted on 14 Jan 2025
275 points (98.2% liked)

Technology

60456 readers
3951 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS
top 27 comments
sorted by: hot top controversial new old
[–] just_another_person@lemmy.world 42 points 11 hours ago (2 children)

Locked bootloader for warranty coverage: totally fine

Refusal for owner to unlock and void warranty: not fine.

[–] Limonene@lemmy.world 43 points 10 hours ago (1 children)

I must disagree. For example, the Magnuson–Moss Warranty Act entitles you to use aftermarket parts in your product without invalidating your warranty, as long as the aftermarket parts don't cause damage. I agree with the spirit of this law, and I believe software should be considered a "part" in this context.

[–] snowsuit2654@lemmy.blahaj.zone -2 points 6 hours ago (2 children)

This is my first time reading about this. I'm very curious to hear a lawyer's thoughts on this.

If you change the bootloader to some other software, how could the software company be expected to provide support for something they may have no knowledge of? Suppose I develop some theoretical SnowsuitOS and then complain to Samsung support when it doesnt run on my smartphone? It seems very likely that some conflict in my code could be causing problems, as opposed to an issue with my hardware.

I feel like to require this, you'd have to prove that the software is functionally equivalent to their software, right? (Side note, isn't this problem undecidable? Program equivalence?)

If you replace a wheel on a tractor you can pretty easily define what it should and should not do. Determining equivalence seems simpler with a physical situation. On the other hand, I'm pretty sure program equivalence is not a solved problem.

My point here is that I don't think it's reasonable to legally require a software company to offer support without limits, because they cannot be sure that there is not an issue with the (unsupported) software you are using.

[–] freeman@sh.itjust.works 2 points 2 hours ago

Nobody is asking 'software' companies to support software they didn't write.

We are asking hardware companies to support their hardware and not use different software as an excuse not to replace faulty hardware.

They can reflash their own software to test if needed.

Of course hardware vendors could be legally mandated to adhere to standards to make things easier.

[–] WhyJiffie@sh.itjust.works 6 points 6 hours ago

If you change the bootloader to some other software, how could the software company be expected to provide support for something they may have no knowledge of?

like xiaomi did, in the past at least. if you can reinstall the official software, you can receive service under warranty

My point here is that I don't think it's reasonable to legally require a software company to

phone manufacturers are hardware companies first and foremost

[–] Zak@lemmy.world 9 points 7 hours ago* (last edited 7 hours ago) (1 children)

In most situations, even that is giving too much power to the manufacturer. It's fair for them to flash the original software as part of any diagnostic or service process, but not fair to refuse to repair or replace a product that actually has a hardware defect just because the owner put different software on it.

[–] WhyJiffie@sh.itjust.works 3 points 6 hours ago (2 children)

It's fair for them to flash the original software as part of any diagnostic or service process

only fair if it does not come with any data loss. so basically not actually fair

[–] itslilith@lemmy.blahaj.zone 5 points 4 hours ago

Backups are, first and foremost, your responsibility. It's unfortunately not realistic to expect someone to diagnose whether an issue is software-related or a hardware failure on any obscure DIY OS you might have installed. But as long as it's possible to flash back the original firmware, warranty should still apply

[–] just_another_person@lemmy.world 3 points 5 hours ago

Software can easily harm the actual device, so locking it to prevent that from happening in a warranty situation doesn't seem super off-base to me.

[–] boreengreen@lemm.ee 51 points 11 hours ago (3 children)

The world would be a better place if locked bootloaders were not a thing. I agree that there needs to be laws in place to prevent the sale of these devices.

[–] henfredemars@infosec.pub 13 points 6 hours ago

I don’t have a problem with boot loaders doing cryptographic checks in general, as long as the ultimate decision lies with the device owner.

[–] Cocodapuf@lemmy.world 2 points 4 hours ago* (last edited 35 minutes ago) (2 children)

How do you feel about locked bootloader's on game consoles?

I figure this is one of those edge cases people might fall on either side of. But consoles are also a really large segment of the tech market, so it's worth thinking about.

[–] Abnorc@lemm.ee 2 points 25 minutes ago

I feel like consoles are targeted at a section of the population that doesn’t value freedom over how they use their hardware. Locked bootloaders on consoles are technically not good, but it’s almost like it’s part of what defines a game console. If it really valued the users freedom, it’d just be a PC. The steam deck and similar devices are changing that idea though.

[–] SomethingBurger@jlai.lu 4 points 1 hour ago

The PS3 used to have an unlocked bootloader with official Linux support. Sony removed it because of piracy. Of course, piracy is still possible, but as always, it's only an excuse to exert more control over customers.

[–] Zak@lemmy.world 47 points 11 hours ago (1 children)

Locked in the technical sense of being able to verify the operating system isn't a bad thing. The problem is when the device owner can't add signing keys of their choice.

The latter is what GrapheneOS does.

[–] Corngood@lemmy.ml 16 points 9 hours ago (1 children)

Something that worries me about that is attestation. This is the advice from the GrapheneOS Devs:

https://grapheneos.org/articles/attestation-compatibility-guide

They're asking app developers to trust their keys specifically, which would mean that the app might work on GrapheneOS, but not my fork of GrapheneOS with some cherry picked fix I want.

It would be much better if we stamped this out now, before all online services require attestation.

[–] Zak@lemmy.world 6 points 8 hours ago

Agreed. Microsoft proposed something along those lines under the name "Palladium" a couple decades ago and was widely criticized, even in the mainstream press. Apple and Google doing the same thing to our phones barely got a whimper.

[–] Imgonnatrythis@sh.itjust.works 74 points 12 hours ago (1 children)

I enjoy your optimism Medhir, but it's more likely in the next five years that people start having their cars remotely bricked than it is any kind of right to root legislation takes off.

[–] LodeMike@lemmy.today 28 points 12 hours ago

That's already a thing, albeit for leases.

[–] palordrolap@fedia.io 9 points 11 hours ago (1 children)

The example picture at the top of the article is weird.

The window title reads "nano" but the software running in the window is Pico, Nano's now deprecated (and strangely-licenced) spiritual parent. Or it's Nano hacked to have a Pico header which, while somewhat fitting with the theme, that would be even more weird.

[–] homesweethomeMrL@lemmy.world 6 points 10 hours ago

*sigh*. What now, Columbo? Y’know I’ve tried to be very helpful you know, with all of your questions, but now it’s becoming very annoying! I’m very busy you know with all my, uh, hacking, as you can plainly see!