4 ms·
> I've always been OK with DRM in apps You want to eat your cake and have it too. DRM is technically impossible, so problems like the one you described are ine
by qb45 9y ago
> I've always been OK with DRM in apps
You want to eat your cake and have it too. DRM is technically impossible, so problems like the one you described are inevitable. Bummer, I guess.
- dante821 9y agoIf DRM is technically impossible, then encryption is technically impossible too... yet we use it.
- dozzie 9y agoDRM is data asking "dear program, please don't let to copy me". It falls apart the moment you have anything to interpret data that doesn't honour this request. Encryption, on the other hand, is a technically sound idea.
- mikevin 9y agoCan you expand on why DRM is technically impossible? I don't disagree but I'm wondering about your reasoning.
- josteink 9y agoIt's about trying to preventing you from accessing encrypted content while having to hand you the key somehow. They are giving you access, so somehow you should be able to get the stream should you want to.
- qb45 9y ago"Impossible" is a bit rhetorical, although in principle the content has to be decrypted to be seen and a Sufficiently Sophisticated Attacker can always somehow extract the decrypted data from the device, in more practical terms this can be made pretty much arbitrarily difficult. What I really meant is that making DRM difficult to crack generally goes against owner control over the machine. The more control you have the easier it is to simply copy the decrypted data or at least attempt exploiting some bugs in the DRM engine if the former is impossible. So we see things like signed bootloaders or dedicated "secure" cores running alongside normal CPUs with some secret firmware on them. In particular, it seems that Android's DRM can be subverted by the bootloader (presumably it uses the ARM TrustZone extension, which is configured by the bootloader and then locked away from the OS) and hence the OP has to choose between DRM and unlocked bootloader.