This affects only KDM and/or CPL XML files - these contain/refer to the expired signer certificate. They can be recreated quickly once a new valid cert has been issued. A new KDM can be ingested as a normal process, a new CPL can only be ingested as another VF. So, if the issue can be fixed with a new KDM, that's as simple as sending out new KDMs for all CPLs. If it's the CPL that is affected (may depend on specific server software), new VFs for all versions have to be created and distributed. These, however, do not need to contain any media assets and can be as small als KDMs and will ingest in no time. They can be sent with the new KDMs necessary anyway in the same email.
MPS just answered to me that new KDMs will be issued. Not sure if that actually means that KDMs alone will solve the issue.
Note that this issue does not exhibit a technical weakness of those affected servers - on the contrary, it means that these servers run fully functional DCI compliant software, while those servers not affected obviously run sloppy software! However, from the exhibitors view, it is of course a benefit to operate a server running sloppy software, at least with respect to security validation ;-)
Also, this issue only happens with SMPTE DCPs, not Interop DCPs.
MPS just answered to me that new KDMs will be issued. Not sure if that actually means that KDMs alone will solve the issue.
Note that this issue does not exhibit a technical weakness of those affected servers - on the contrary, it means that these servers run fully functional DCI compliant software, while those servers not affected obviously run sloppy software! However, from the exhibitors view, it is of course a benefit to operate a server running sloppy software, at least with respect to security validation ;-)
Also, this issue only happens with SMPTE DCPs, not Interop DCPs.
Comment