6 ms·
Wouldn't this DRM require every implementation of the JPEG standard to honor the DRM or am I missing something?
by Spivak 11y ago
Wouldn't this DRM require every implementation of the JPEG standard to honor the DRM or am I missing something?
- TD-Linux 11y agoYes it would - but that's how all DRM systems work, plus an attempt to make the image unreadable to "unauthorized" JPEG implementations.
- bediger4000 11y agoHow, if some Future JPEG (FJPEG) is a standard, does one make a standard FJPEG image unreadable to unauthorized FJPEG implementations? Either the standard itself has to be kept secret or the FJPEG implementation has to contain some secret, right? If the standard is kept secret, by maybe charging a tidy sum for it, and getting all buyers to sign an NDA in blood, we'll all have fewer implementations of FJPEG viewers. There would probably be no "open source" implementations of FJPEG. We would all loose, as the market for FJPEG viewers has barriers to entry, and therefore would serve buyers poorly. That's standard, Free Market economics. If FJPEG viewers have to contain some secret (an algorithm or a key both come to mind as things that have happened in the past) the same sorts of things happen - barriers to entry to sell in the market, higher costs, fewer options to consumers. Of course the 3rd option is to legally mandate some kind of overall DRM at the operating system level, which would have much the same effects, except that we'd have a narrow choice of Windows or Mac OS, with maybe a larger choice of FJPEG viewers. All of these options should be repugnant to Free Market believers such as myself. I predict the Republican Congress will laugh this out the door.
- airza 11y agoJust like they did with the DMCA, right?
- bediger4000 11y agoI'm sorry, but could you elaborate on this? I'm not understanding the connection with DMCA.
- TD-Linux 11y agoYeah, those are the only options. The second option is what Blu-Ray and EME currently do, for example. But yeah, basically no one is going to use this ever.
- nickodell 11y agoNo, that would be unenforceable. If your implementation doesn't honor the DRM, they won't provide you with the encryption keys in the first place.
- MichaelGG 11y agoThen you end up with a key distro problem. And unless the idea is to do it with hardware-protected keys, it's pretty much DOA for such low-bandwidth, simple-format as a still picture. Otherwise, as an example, Firefox wouldn't be able to decode these images without some plugin. And that plugin would be just as subject to key-dumping.
- ekimekim 11y agoYes, all DRM systems are inherently impossible to make fully secure with only local data. However, several other options exist: * Needing to contact an external server to view an image (of course, you could always take the opportunity to save the now-viewable image then share it) * Charging a large fee / legal contracts for the information on how to decode (security through obscurity) * Making circumvention illegal and enforcing this with fines or jail time. This is probably the only option that "actually works" as you've turned the technical problem into a social problem. People would still break it, but you could simply arrest them if they try to help others do the same.
- MichaelGG 11y agoI'm not sure these approaches work for images. Certainly web comics could require special clients even now, yet they don't. I'm guessing they want the ability for their pictures to still work normally, but "without saving".
- ekimekim 11y agoYes, that none of these systems will ever actually work is the point ;)
- 11y ago
- mzs 11y agoNot necessarily, for example a few MSBs of Y, Cr, and Cb DC and AC could be encoded with the current JFIF markers and new ones used the for rest in an encrypted representation. In that manner a current decoder could produce a lower fidelity version still: http://www.jpeg.org/items/20150910_privacy_security_summary.html http://www.jpeg.org/items/20150910_privacy_security_summary....