|This FAQ is valid for|
Beginning with version 2.1, easyDCP Creator+ is capable of opening encrypted DCPs and using these DCPs as basis for new DCPs. There are basically two ways of providing the keys in order to allow easyDCP Creator+ to decrypt the content for the preview and for generating a new DCP.
If keys are provided by means of a proprietary Fraunhofer Digest file (*.dcpdig), it is assumed that the user generated the content and that he is in charge of the sources used for the original DCP generation. In this case you can alter all properties in easyDCP Creator+, including the deactivation of the encryption or the generation of a new encrypted DCP and Digest file.
If one provides the keys by means of Distribution KDM (or KDM), easyDCP Creator+ does not allow to disable the encryption nor does it generate the Fraunhofer Digest for the new DCP. In order to understand this behavior we have to explain that the Fraunhofer Digest stores the encryption key as plain text on the hard drive. If the Digest-option were not disabled, one could easily open an encrypted DCP together with a (D)KDM, generate a new encrypted DCP and store the encryption keys in plaintext. Since content-owners are very diligent with their content, Fraunhofer IIS decided to disable the option from the beginning.
Since the software does not permit you to generate a Digest, there has to be another way for communicating the encryption keys to another software. Using easyDCP Creator+ version 2.1 or higher this can be done by generating a (D)KDM directly from within easyDCP Creator+. The “Generate DCP…” dialog was extended to offer you to generate KDMs. By design, one (D)KDM will be generated for easyDCP Creator+ itself in order to make sure that one can open the DCP on the same computer using easyDCP Creator+ later.
A second (D)KDM can be generated for another software being able to open (D)KDMs, including easyDCP KDM Generator+ and many other 3rd party hard-/and software tools.