View Bug Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001066 | DCP-o-matic | Features | public | 2017-04-30 00:55 | 2018-10-17 20:13 |
Reporter | carl | Assigned To | carl | ||
Priority | high | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Summary | 0001066: Should make it clearer which data must be preserved when making encrypted DCPs | ||||
Description | e.g. private key when making DKDMs, otherwise metadata.xml (I think). See http://www.dcpomatic.com/forum/viewtopic.php?f=2&t=792 | ||||
Tags | No tags attached. | ||||
Branch | |||||
Estimated weeks required | |||||
Estimated work required | Unknown | ||||
|
I think it would be better to keep preferences.xml. This allows to return reinstalled DOM to the state it was before reinstallation with all the certificates, keys and DKDMs preserved. |
|
Yes, except if you make an encrypted DCP but then don't save the metadata.xml and don't make a DKDM; the DCP is still useless. |
|
bb80004d3201047a33dd251ea6c3f6de2b47cb3b adds a nag to backup config.xml if you make a DKDM. |
|
2ff11f911be705b33c272cee0c8a42594e7bcd84 nags about making encrypted DCPs. |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-04-30 00:55 | carl | New Bug | |
2017-04-30 00:55 | carl | Status | new => assigned |
2017-04-30 00:55 | carl | Assigned To | => carl |
2017-05-01 07:14 | scorpio81 | Note Added: 0001640 | |
2017-05-01 22:54 | carl | Note Added: 0001641 | |
2017-05-04 10:56 | carl | Note Added: 0001649 | |
2017-05-04 11:59 | carl | Note Added: 0001650 | |
2017-05-04 11:59 | carl | Status | assigned => resolved |
2017-05-04 11:59 | carl | Resolution | open => fixed |
2018-10-17 20:13 | carl | Status | resolved => closed |