3 ms·
I don't see how your points are responsive. The fact that it's "on purpose" (of course it's on purpose!) doesn't changes RMS's argument that it's unethical and
by ajross 15y ago
I don't see how your points are responsive. The fact that it's "on purpose" (of course it's on purpose!) doesn't changes RMS's argument that it's unethical and abusable. Your examples aren't "malicious", but it seems awfully naive to believe these are the only applications of that technology.
And I don't think Stallman has anything against network-delivered software. He's been doing that for years. The complaint I read was about the ability of the carrier to install things without user authorization, and to use authorization to remove/modify existing features in a way that cannot be recovered. Both of those have happened in the wild.
- cube13 15y agoThe main issue that I have with this specific issue that RMS is making an ideological argument that I don't feel is realistic. He states the following: >Putting these points together, we can tolerate non-free phone network firmware provided new versions of it won't be loaded, it can't take control of the main computer, and it can only communicate when and as the free operating system chooses to let it communicate. The problem here is that the phone component needs to be able to override the rest of the OS to receive a call. To suggest otherwise is a pretty huge potential privacy issue... would you want every application to have access to the phone firmware? In addition, the phone firmware exists to make the phone actually work with a specific carrier. So it needs to have control of the microphone, the speakers, and the radio in order to function. That requirement exists in both a closed implementation, and a FOSS implementation. Therefore, a FOSS firmware implementation still has the exact same potential issues that RMS raised-complete control of the hardware, the ability to restrict the user from doing certain actions, the potential of using the device to spy on people through well obfuscated(or buggy) code, etc. Some of the more malicious uses are mitigated by a FOSS implementation, I will agree. However, I don't think that RMS has a solution that actually solves any of the issues that he raised.
- Dylan16807 15y agoIt's the job of the operating system to control what applications have access to. The firmware does not need to override anything. The OS should either implement a phone component or delegate to a phone app that has been configured to have phone permission. Binary blob completley-isolated firmware is possible and simple to implement. It's also safe.