View Bug Details

IDProjectCategoryView StatusLast Update
0001156DCP-o-maticBugspublic2021-01-08 00:45
Reportercarl Assigned Tocarl  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionunable to reproduce 
Summary0001156: Crash on import of a KDM decryption chain private key
Description
  1. Export the Signing DCPs and KDM Certificate from Machine A
  2. Export the KDM Decryption Certificate from Machine A
  3. Export the KDM Decryption Chain Certificate from Machine A
  4. Copy the 3 files from the steps above to Machine B
  5. Open the keys tab on DOM. Load the Signing DCP Key <--- An error in red will appear indicacting
  6. Load the KDM Decryption Chain Key .... Crashes at this stage. Error message is as below

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Both running 2.11.34; Machine A is Windows 10, B is Windows XP.

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredUnknown

Activities

Carsten

2018-01-06 00:09

manager   ~0001920

Maybe we need a simpler/safer way to handle certificates during import and export. Remains a fact though, that some things simply are and remain complicated. You can not build a jet turbine with a mouse click.

  • Carsten

Guddu

2018-01-06 00:40

reporter   ~0001922

Carsten, I personally find the current form page simple....Just that it should work instead of erroring out. Also there is a way to export KDM Decryption change but no way to load/import it back. At the moment copying the config.xml is the only way to have this work on different machines whereas it should be handled by key imports and exports.

Carsten

2018-01-06 03:40

manager   ~0001927

Guddu - I think it would be better to be able to export and import the whole certificates and keys in one go. The current dialog works for people who already know about many aspects of certs and KDMs. It should be easier for beginners to keep their certs safe as well. The trouble with having them in the config file is, as we have seen, the config file may become incompatible between versions, and then the certs and keys can not be recovered easily. In your case, we recommended to go back to 2.10.5 from 2.11.34, but as the config file is not backwards compatible, you had no ways to get your certificates from a 2.11.34 installation into a 2.10.5 installation, hence you were forced to use a test version for production work.

  • Carsten

carl

2018-03-02 22:35

administrator   ~0002264

@Guddu: things should be simpler in current test versions, and I can't reproduce that crash now on Windows XP. Can you test it out and see if you can?

https://dcpomatic.com/test-download

carl

2018-03-10 00:47

administrator   ~0002288

Unhooking from 2.12.0 until we hear some feedback.

Bug History

Date Modified Username Field Change
2018-01-05 22:20 carl New Bug
2018-01-06 00:09 Carsten Note Added: 0001920
2018-01-06 00:40 Guddu Note Added: 0001922
2018-01-06 03:40 Carsten Note Added: 0001927
2018-03-02 22:35 carl Note Added: 0002264
2018-03-02 22:35 carl Assigned To => carl
2018-03-02 22:35 carl Status new => feedback
2018-03-10 00:47 carl Target Version 2.12.0 =>
2018-03-10 00:47 carl Note Added: 0002288
2019-11-17 21:50 carl Status feedback => resolved
2019-11-17 21:50 carl Resolution open => unable to reproduce
2021-01-08 00:45 carl Status resolved => closed