3 ms·
> trusted execution of code in an untrusted environment This implies taking power and control away from the user. Trusted execution means execution the user ca
by matheusmoreira 6y ago
> trusted execution of code in an untrusted environment
This implies taking power and control away from the user. Trusted execution means execution the user can't tamper with or analyze as well as memory the user has no access to. The user's own machine has been sealed off.
It's not just DRM. From a computing freedom point of view, all trusted computing is bad. It prevents legitimate activities like reverse enfineering proprietary software in order to create a free software replacement.
Trusted by whom? Invariably it's the company making the software. Users are never empowered by this. Corporations are already in a position of power over most people, we don't need even more technology that gives them even more control. Imagine if this becomes common enough to show up in browsers and the web. Suddenly inspect element and view source no longer work, scripts and ads cannot be blocked and extensions become a thing of the past. All in the name of corporate control.
- wmf 6y agoYou're presenting one situation: someone else's code running in the user's environment. But what about running the user's code in someone else's untrusted environment?
- akersten 6y agoIn my opinion, the idea there is the same as it's always been: don't trust the client.
- lxgr 6y agoSGX is mostly about servers, not clients.
- matheusmoreira 6y ago> someone else's untrusted environment That "someone else" should have the same powers over their machines that users do. They should be allowed to see everything and tamper with anything. After all, the computer is theirs. Other people's computers should always be untrusted.
- johncolanduoni 6y agoDo you feel the same way about cloud providers? Should they always be able to see everything and tamper with anything for the workloads their users run? If that’s the case, would you be in favor of making contracts to that effect (as already exist for all cloud providers I’m aware of) unenforceable?
- matheusmoreira 6y agoI agree that trusted computing can be a good thing for cloud computing providers. They own the computer hardware but other people are paying them in order to use those resources. That's the entire point of cloud computing. The user and owner of the hardware are different people and so offering trusted computing as a feature makes sense. Consumers are the opposite: they pay companies in order to use their software on their computers. The owner and user of the machine are the same person. Users should get to maintain complete control over the hardware, including the ability to reverse engineer the software and even make "unauthorized" copies of anything they want. I don't trust that this technology will be restricted to cloud computing though. The copyright industry is worth billions of dollars. They'll make use of it on consumer machines if it's available. This is something that should be prevented at all costs, since the worst case scenario is a world where all commercial software runs in a secure execution environment where the user has no control. Threat models where the user is an adversary are obviously user hostile. So of course whenever these technologies are compromised it is a victory for software freedom.
- lxgr 6y ago> Users should get to maintain complete control over the hardware, including the ability to reverse engineer the software Secure enclaves and auditable software are not mutually exclusive. It's totally possible to run open source software in an enclave! > the worst case scenario is a world where all commercial software runs in a secure execution environment where the user has no control. This would be a very bad scenario indeed, but I consider it completely unrealistic. The trusted computing base of an entire graphical computing device including its operating system and all installed applications is absolutely impossible to audit. It didn't work for Microsoft (Palladium), and it's also not the direction that Apple is going, arguably one of the most restrictive client platforms today. Practical trusted computing are tiny (and ideally heavily sandboxed!) trusted enclaves running the least amount of critical, audited code.
- pmontra 6y agoI'm more concerned about this scenario: running my program A on my machine side by side with somebody's else program B that I don't fully trust. Your scenario looks like the authors of program B not trusting me. Sorry for them but it's my machine.