View Bug Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000608 | DCP-o-matic | Features | public | 2015-06-16 09:14 | 2016-05-31 23:57 |
Reporter | carl | Assigned To | carl | ||
Priority | high | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Target Version | 2.5.0 | ||||
Summary | 0000608: Better KDM management using DKDMs | ||||
Description | I think it would be better, instead of the current arrangement to create a DKDM for the user's key when an encrypted DCP is made. Then store this somewhere (in the film folder or in metadata.xml) and use it to create KDMs. This would allow an easy split of the KDM generator to a different program: give it the DKDM and it would have everything it needed. | ||||
Tags | No tags attached. | ||||
Branch | |||||
Estimated weeks required | |||||
Estimated work required | Average | ||||
|
Only snag is if you change the DCP-o-matic key a previously-stored DKDM will no longer work. Similarly opening a project on a different computer will not allow you to create a KDM. I think this is too nasty to consider; DKDM stuff should be separate. |
Date Modified | Username | Field | Change |
---|---|---|---|
2015-06-16 09:14 | carl | New Bug | |
2015-06-16 09:14 | carl | Relationship added | related to 0000330 |
2015-06-16 09:14 | carl | Relationship added | related to 0000561 |
2015-09-01 22:58 | carl | Priority | normal => high |
2015-09-01 22:58 | carl | Status | new => acknowledged |
2015-10-05 12:37 | carl | Note Added: 0000898 | |
2015-10-06 11:50 | carl | Target Version | 2.x => 2.5.0 |
2015-10-06 11:51 | carl | Note Edited: 0000898 | |
2015-11-04 00:54 | carl | Status | acknowledged => resolved |
2015-11-04 00:54 | carl | Resolution | open => fixed |
2015-11-04 00:54 | carl | Assigned To | => carl |
2016-05-31 23:57 | carl | Status | resolved => closed |