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.
But yeah, basically no one is going to use this ever.
http://www.jpeg.org/items/20150910_privacy_security_summary....
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.
Not if you are running a skylake CPU with the new SGX instructions that encrypt RAM.
https://software.intel.com/en-us/blogs/2013/09/26/protecting...
6, Enable software vendors to deliver trusted applications and updates
8. Enable applications to define secure regions of code and data that
maintain confidentiality even when an attacker has physical control
of the platform and can conduct direct attacks on memory.
By "trusted", Intel almost certainly means "trusted computing"/"trusted execution environment". It took a decade, but Palladium (NGSCB) is here.Firefox already caved and ships the EME plugin, so obviously they would cave to an image-DRM plugin as well.
/* this is why it's so incre4dibly important to take a hard-line stance against DRM; it's a lot harder to reverse course once you cave and start accepting some DRM */
I agree that they may expand it (MS's waste of engineers during the Vista period in their rush to provide Protected Media Path comes to mind.)
But I'm also saying that web comics could do this today. But I'm guessing that they don't want to sacrifice the UI of just loading images.
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.