Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's perfectly okay for you to put GPLv3 software in ROM that nobody can ever modify and then sell me the hardware. What's not okay is selling me hardware where you can modify the software after the fact, but I can't. And it's also okay for your hardware to detect if I modified the software. It just can't refuse to work if I did.


And this is where the FSF makes the weird trade off that they prefer to not have security updates as that's more "free" than being able to get security updates from the manufacturer. Either way you can't update it, but at least in the scenario the FSF opposes the users are able to be more secure.


True. FSF doesn't support taking the freedom away from users in the name of security.

> at least in the scenario the FSF opposes the users are able to be more secure

That's quite questionable. What if someone steals the manufacturer keys? Then people with unmodifyable devices would be more secure.

But anyway that's besides the point since FSF is against taking the freedom away from the users under the veil of "security" anyway.


That's not what the FSF meant the exception to be used for. That's basically the manufacturers abusing a loophole.


this has nothing to do with security updates. any vendor is free to ship security updates however vendors often decide to refuse updates to "tainted" devices.


that scenario doesn't exist, non-flashable rom.

only. the other scenario, "vendor can update I can't" is relevant.

and that detection mechanism is called "secure boot".


> that scenario doesn't exist, non-flashable rom.

Of course they do. One example is pressed DVDs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: