I understand having a locked-down version of mass-produced tech that is for the general consumer. However, I also firmly believe that anyone who wants to should be able to bypass that. Make it void the warranty, don't allow customer support, whatever you want. But make it a free option to have complete control. If I buy a piece of hardware, I should own it.
(I say this as I am currently charging a cheap doorbell camera I bought, so that I can start dumping data from it and reverse engineer its protocol, solely so that I can lock it down to my local network...We needed something at the time, or I would have bought something more expensive that had an open protocol...)
> Make it void the warranty, don't allow customer support, whatever you want.
That would be a regression in terms of consumer rights, in my opinion. I don’t see why the EU shouldn’t legislate such that the right to control owned hardware becomes fundamental.
Technically, even in the US a warranty is only void if it's caused by something the consumer did; a 1 year warranty for production defects can't be voided.
Although I think it's fair that the company not have to deal with a defect that is almost certainly caused by something you do to your device. Like, strawman, but early iPhones sometimes encountered issues while doing an untethered jailbreak, or people would install tweaks that were less than stable (even sometimes on relatives' or friends' phones), then they would walk into an Apple Store with weird behavior and expect the fix to be free. That shouldn't be covered by warranty.
In large, powerful and potentially dangerous machines, the firmware may embody safety features. Like preventing dangerous doses of radiation or overspeed conditions on motors or overcharging of batteries.
Why should you have a right to operate the device in a dangerous way that the manufacturer engineered to prevent?
You may be happy to injure yourself and to disclaim your right to warranty but the manufacturer could suffer immense reputational damage if, say, your hacking the firmware of their humanoid robot results in it tearing off your head.
That reminds of this company that used to provide a body implant for people with certain issues. The company ended up closing down and had to go in and remove those implants from those people.
Those people rightfully were like why can’t we keep it and the company was like we have to run the services to manage it. Why not just open up the hardware and let it continue being used? Well if you put the wrong software and it ends up killing the person, the hardware company can be held liable.
Made me realize my dream of having an open-source car is never going to happen.
From the perspective of a researcher: there is a clear 'yes'. Void the warranty, make sure all certification for operarion is invalid.
That is to a certain point. If deemed misuse would be harm against other people or circumvent export control. You may also restrict, who is allowed to do it. However, if software is the only protection against dual-use, tler might have a general problem.
When people get a tool, they can perfectly well hurt themselves with it.
But at the same time, risk profiles between different tools are different, and it is common to have special rules for some of them. Eg. guns already do.
While we might need to stop an unlicensed SW engineer to accidentally or purposely turn your housekeeping robot into a killer robot, the risk of them messing up their fridge is lower. Yes, your food could spoil and kill you, but your fridge could face a power cut and do the same.
So establish which devices have a higher risk and limit changes to those with more expertise — if it means licensed engineers, so be it.
There are a lot of devices where I agree with you, but smart glasses are an appliance category where this categorically needs to be considered a vulnerability. The main thing that currently stands between them being truly amazing and useful (e.g. for people with impaired vision or hearing) and a spying/peeping tool is the firmware on the device.
Smartglasses have an amazing potential to improve lives when done right and used right. But that relies on a sophisticated sensor hardware package that is barely distinguishable from a covert recording tool, simply because of the reality of the problem space. I don't want to see that tech totally canned as assistive technology because of backlash.
I think this is an area where society is going to adjust to fit the technology. The idea that you can not be recorded in places where eyeballs can see you is going to seem pretty quaint before long. Uncomfortable to our sensibilities, but probably not uncomfortable after the next few generations.
You’re describing a dystopia. Being constantly recorded is not “uncomfortable”, it’s a violation of our private space and changes our behaviour. There are several studies on the psychology of being recorded.
We’ll never improve society as long as we keep rolling over and saying “it’s the way it’s going to be, we just have to adjust”. Nothing made by humans is inevitable. Chat Control having been repeatedly repealed is proof that resistance is not futile. We’re in a bad spot, yes, but we should fight to defeat the bad outcomes or delay them as much as possible.
I think the current line in the sand is surreptitious recording with their glasses and the light. They have anti-tamper stuff around that, and I can see why they intentionally make root difficult.
People don't like recording, and there's usually a patchwork of laws that give many people some protection against it.
Not related to meta but the privacy angle is stuff like the Plaud recorders. Normal non-techies have had these, including personal run-ins of my own with people using these dedicated smartphone recorders where it was neither acceptable nor consensual.
I'm curious if ubiquitous and hidden personal recording collapses the technical or social lines set up against it first.
I am a proponent of giving users an option to root their devices through a one-way process that would surrender warranty coverage and print a big safety warning at every boot.
The problem with allowing easy shell access is that any arbitrary command execution would be used by exploits, too. There are also a lot of social engineering schemes that bait users into running commands on devices. We don’t think about these risks as engineers, but you wouldn’t believe how many people will follow instructions to open something like the Chrome developer console and paste code blocks into it because some website told them to.
So a secure device is also a locked down device. Getting a shell is a vulnerability because it’s the avenue that exploits would use.
That’s why I’d be in favor of a one-way developer mode, which provided shell access but printed a big unavoidable warning screen in the boot loader.
Unfortunately, it’s not that simple. Asking people to give up their warrant isn’t legal, generally, so outside of very specific circumstances you have to cover warranty claims on the device, too. I have worked at companies that tried to offer some developer access like this, and the number of people abusing customer service because they got in over their heads with modifications and wanted a fresh unit or want CS to support their mods would make you face palm. So the compromises end up being things like only allowing ephemeral mods that get wiped at each reboot and other default-safe behaviors, but that doesn’t make people happy either.
Following the reasoning behind the magnuson-moss act, it should not automatically void the warranty. That puts users who want software freedom at a financial disadvantage.
I agree some big obvious scare message is good but actually voiding the warranty restricts user freedom.
> Following the reasoning behind the magnuson-moss act, it should not automatically void the warranty. That puts users who want software freedom at a financial disadvantage.
Only thing is, if the company releases software updates to fix issues, they should by no means be expected/required to backport bug fixes to older versions just so that compromised devices can. There are certain warranty claims where the issues would be solved via software update, but thus are unavailable to people who are insistent on staying on a rootable version of the firmware.
Do I really "have root" if you've put an "unavoidable warning" in the bootloader that I can't remove? It sounds like you're still asserting primary control over the device and giving me a limited playground. Your suggestion is "we're going to run code you don't control on your device, and it's going to run before any of your code, and there's nothing you can do about it, but don't worry we pinky promise to only make it print a warning scolding you for wanting root."
Nah. No thanks. I want actual freedom, not a longer chain.
I understand having a locked-down version of mass-produced tech that is for the general consumer. However, I also firmly believe that anyone who wants to should be able to bypass that. Make it void the warranty, don't allow customer support, whatever you want. But make it a free option to have complete control. If I buy a piece of hardware, I should own it.
(I say this as I am currently charging a cheap doorbell camera I bought, so that I can start dumping data from it and reverse engineer its protocol, solely so that I can lock it down to my local network...We needed something at the time, or I would have bought something more expensive that had an open protocol...)
> Make it void the warranty, don't allow customer support, whatever you want.
That would be a regression in terms of consumer rights, in my opinion. I don’t see why the EU shouldn’t legislate such that the right to control owned hardware becomes fundamental.
Technically, even in the US a warranty is only void if it's caused by something the consumer did; a 1 year warranty for production defects can't be voided.
Although I think it's fair that the company not have to deal with a defect that is almost certainly caused by something you do to your device. Like, strawman, but early iPhones sometimes encountered issues while doing an untethered jailbreak, or people would install tweaks that were less than stable (even sometimes on relatives' or friends' phones), then they would walk into an Apple Store with weird behavior and expect the fix to be free. That shouldn't be covered by warranty.
2 replies →
In large, powerful and potentially dangerous machines, the firmware may embody safety features. Like preventing dangerous doses of radiation or overspeed conditions on motors or overcharging of batteries.
Why should you have a right to operate the device in a dangerous way that the manufacturer engineered to prevent?
You may be happy to injure yourself and to disclaim your right to warranty but the manufacturer could suffer immense reputational damage if, say, your hacking the firmware of their humanoid robot results in it tearing off your head.
That reminds of this company that used to provide a body implant for people with certain issues. The company ended up closing down and had to go in and remove those implants from those people.
Those people rightfully were like why can’t we keep it and the company was like we have to run the services to manage it. Why not just open up the hardware and let it continue being used? Well if you put the wrong software and it ends up killing the person, the hardware company can be held liable.
Made me realize my dream of having an open-source car is never going to happen.
3 replies →
From the perspective of a researcher: there is a clear 'yes'. Void the warranty, make sure all certification for operarion is invalid.
That is to a certain point. If deemed misuse would be harm against other people or circumvent export control. You may also restrict, who is allowed to do it. However, if software is the only protection against dual-use, tler might have a general problem.
[dead]
When people get a tool, they can perfectly well hurt themselves with it.
But at the same time, risk profiles between different tools are different, and it is common to have special rules for some of them. Eg. guns already do.
While we might need to stop an unlicensed SW engineer to accidentally or purposely turn your housekeeping robot into a killer robot, the risk of them messing up their fridge is lower. Yes, your food could spoil and kill you, but your fridge could face a power cut and do the same.
So establish which devices have a higher risk and limit changes to those with more expertise — if it means licensed engineers, so be it.
2 replies →
[flagged]
There are a lot of devices where I agree with you, but smart glasses are an appliance category where this categorically needs to be considered a vulnerability. The main thing that currently stands between them being truly amazing and useful (e.g. for people with impaired vision or hearing) and a spying/peeping tool is the firmware on the device.
Smartglasses have an amazing potential to improve lives when done right and used right. But that relies on a sophisticated sensor hardware package that is barely distinguishable from a covert recording tool, simply because of the reality of the problem space. I don't want to see that tech totally canned as assistive technology because of backlash.
I think this is an area where society is going to adjust to fit the technology. The idea that you can not be recorded in places where eyeballs can see you is going to seem pretty quaint before long. Uncomfortable to our sensibilities, but probably not uncomfortable after the next few generations.
You’re describing a dystopia. Being constantly recorded is not “uncomfortable”, it’s a violation of our private space and changes our behaviour. There are several studies on the psychology of being recorded.
We’ll never improve society as long as we keep rolling over and saying “it’s the way it’s going to be, we just have to adjust”. Nothing made by humans is inevitable. Chat Control having been repeatedly repealed is proof that resistance is not futile. We’re in a bad spot, yes, but we should fight to defeat the bad outcomes or delay them as much as possible.
3 replies →
I think the difference between improving lives and spying is having the glasses be completely obvious about their purpose.
Would people using them because of visual impairment be OK with them being bright green?
Most of them wouldn't be OK with that because that serves as a marker that triggers alienating behaviors in others.
1 reply →
I think the current line in the sand is surreptitious recording with their glasses and the light. They have anti-tamper stuff around that, and I can see why they intentionally make root difficult.
https://www.theverge.com/gadgets/962514/meta-privacy-light-t...
People don't like recording, and there's usually a patchwork of laws that give many people some protection against it.
Not related to meta but the privacy angle is stuff like the Plaud recorders. Normal non-techies have had these, including personal run-ins of my own with people using these dedicated smartphone recorders where it was neither acceptable nor consensual.
I'm curious if ubiquitous and hidden personal recording collapses the technical or social lines set up against it first.
I am a proponent of giving users an option to root their devices through a one-way process that would surrender warranty coverage and print a big safety warning at every boot.
The problem with allowing easy shell access is that any arbitrary command execution would be used by exploits, too. There are also a lot of social engineering schemes that bait users into running commands on devices. We don’t think about these risks as engineers, but you wouldn’t believe how many people will follow instructions to open something like the Chrome developer console and paste code blocks into it because some website told them to.
So a secure device is also a locked down device. Getting a shell is a vulnerability because it’s the avenue that exploits would use.
That’s why I’d be in favor of a one-way developer mode, which provided shell access but printed a big unavoidable warning screen in the boot loader.
Unfortunately, it’s not that simple. Asking people to give up their warrant isn’t legal, generally, so outside of very specific circumstances you have to cover warranty claims on the device, too. I have worked at companies that tried to offer some developer access like this, and the number of people abusing customer service because they got in over their heads with modifications and wanted a fresh unit or want CS to support their mods would make you face palm. So the compromises end up being things like only allowing ephemeral mods that get wiped at each reboot and other default-safe behaviors, but that doesn’t make people happy either.
Following the reasoning behind the magnuson-moss act, it should not automatically void the warranty. That puts users who want software freedom at a financial disadvantage.
I agree some big obvious scare message is good but actually voiding the warranty restricts user freedom.
> Following the reasoning behind the magnuson-moss act, it should not automatically void the warranty. That puts users who want software freedom at a financial disadvantage.
Only thing is, if the company releases software updates to fix issues, they should by no means be expected/required to backport bug fixes to older versions just so that compromised devices can. There are certain warranty claims where the issues would be solved via software update, but thus are unavailable to people who are insistent on staying on a rootable version of the firmware.
1 reply →
"They might do something stupid with it" is just authoritarian. You would take our sticks
Okay but that's how so many systems including banking are set up to safeguard users
When something goes wrong, they blame you. They don’t care if anything they did caused it.
> You would take our sticks
Did you just completely ignore the entire point of my comment where I said I advocate giving people developer access?
Have all the sticks you want, but don’t come crying to the company if you hurt yourself.
1 reply →
Do I really "have root" if you've put an "unavoidable warning" in the bootloader that I can't remove? It sounds like you're still asserting primary control over the device and giving me a limited playground. Your suggestion is "we're going to run code you don't control on your device, and it's going to run before any of your code, and there's nothing you can do about it, but don't worry we pinky promise to only make it print a warning scolding you for wanting root."
Nah. No thanks. I want actual freedom, not a longer chain.
> bait users into running commands on devices. We don’t think about these risks as engineers
As an engineer, you wouldn't believe how many times I've recently used `curl | bash` to install a piece of software
[flagged]