2 ms·
OK, that still doesn't mean it's a good idea to say that some useful new combination of PGP, TLS and AES-NI is "DRM." You do realize that DRM started out basic
by stcredzero 12y ago
OK, that still doesn't mean it's a good idea to say that some useful new combination of PGP, TLS and AES-NI is "DRM."
You do realize that DRM started out basically as trusted execution, and that the other layers of meaning you're piling on are just politics?
It's not "fluffy sentiment" to believe that words mean what other people understand them to mean.
Okay then. Global Warming is a debate, vaccines are harmful, and people freeze instantly when they step into vacuum, then.
If you want to start a new nation-wide left-leaning political party, calling it the National Socialist Party is a Bad Idea, regardless of whether it satisfies each of the characteristics of being national, socialist, and a political party.
Yes, but if you have the intellectual wherewithal to discuss nationalism and socialism, I expect you to follow suit in the discussion, not to knee-jerk about Nazism.
> Also, aren't you a member of TX/RX?
Why, is there someone there impersonating me?
Oh, so you're not that Anthony.
- AnthonyMouse 12y ago> Okay then. Global Warming is a debate, vaccines are harmful, and people freeze instantly when they step into vacuum, then. Those aren't issues of word meaning. The issue there is not a disagreement about what Global Warming is or what a vaccine is. Here, I'll demonstrate by solving the problem at hand and distinguishing "DRM" from the solution. The problem is that you have a piece of software that needs to update itself periodically, but the software has access to sensitive data (private keys) and the updates are sufficiently frequent that verifying each of them is unmanageable. Let's sketch out a solution. The thing you need is to separate the sensitive bits from the other bits, so you can update the other bits without worrying about your private key. One possible solution is for computers to be sold with a TPM that comes from the factory with a private key in it, and have the TPM as the thing that does the sensitive bits so that unless the TPM is broken the browser plugin can't get a copy of your private key. This solution is terrible. If the private key is there from the factory then you don't know that the manufacturer doesn't have a copy of it, or that it wasn't generated with Dual EC DBRG, or that the TPM is doing what it's supposed to be doing and doesn't have an intentional backdoor or accidental security vulnerability. If you can't get the key out even as root then you can't copy it for when your hardware dies or becomes obsolete. And if there is a security flaw in the TPM then you can't fix it, you have to throw away the device (with the key) and buy a new one. The only reason to put any keys there from the factory and incur all of these disadvantages is to try to secure the device against the user. There is no benefit to the user of doing it that way. Let's try a different solution. You run the browser and its plugins in a virtualization sandbox. The sandbox has an API for signing messages. The PGP plugin can request signing and provide a copy of the message to be signed. The OS or hypervisor then removes the sandboxed code from the CPU and runs a small, privileged application the purpose of which is solely to display the message to be signed, get your approval, and produce a signed message for the sandbox if you approve. It does nothing else, so it very rarely needs to be updated, but it can be, and when it is the code is short and simple and the changes are small, making updates much easier to validate. The privileged code is secure against browsers and plugins but not against the owner of the device, so you can backup the keys or transfer them to another device at your pleasure, and you generated the keys to begin with so you know where they came from. These are two very different solutions and it is important to distinguish one from the other. Whatever five researchers thought DRM meant a decade ago is no longer important. Today it has a certain connotation which is decidedly negative. If you have something beneficial, calling it DRM only serves to sully its reputation by association with the user-hostile things that have historically been called DRM.