View Bug Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001017||DCP-o-matic||[All Projects] Features||public||2016-11-23 10:41||2016-11-25 09:14|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0001017: Import of dcp made with the same server should get its kdm auomatically|
When importing a DCP into Dom if the DCP as been made with the same machine it should be automatically accepted without having to ingest a KDM for it.
|Tags||No tags attached.|
|Estimated work required||Average|
You mean if a DKDM has already been made for the imported DCP?
No I mean , why having to make a DKDM for a DCP when this one has been created on this machine by DoM? It make sense that this DCP is secure on the machine.
The necessary decryption key is held in the metadata.xml of the project that created the DCP. I think what you are suggesting would mean that DoM would need a database of every key that has been used along with the CPL ID. This seems like a somewhat unnecessary security risk to me, unless I am missing something?
This is the way Cineasset is working, when you encrypt a DCP on your PC using your certificates, then you can read it and re-encrypt it without creating a DKDM for it.
|2016-11-23 10:41||jjmantello||New Bug|
|2016-11-23 10:58||carl||Note Added: 0001556|
|2016-11-23 10:58||carl||Assigned To||=> carl|
|2016-11-23 10:58||carl||Status||new => feedback|
|2016-11-23 11:18||jjmantello||Note Added: 0001558|
|2016-11-23 11:18||jjmantello||Status||feedback => assigned|
|2016-11-23 11:47||carl||Note Added: 0001559|
|2016-11-23 11:47||carl||Status||assigned => feedback|
|2016-11-23 12:11||jjmantello||Note Added: 0001562|
|2016-11-23 12:11||jjmantello||Status||feedback => assigned|