2.16.10 Can't open encrypted DCP

nimes · Post by **nimes** » Sat May 21, 2022 2:16 pm

Both the DCP Player and DCP encoder of version 2.16.10 can't open the encrypted DCP encrypted by its own encoder. An error message opens while opening those encrypted DCPs.

Carsten · Post by **Carsten** » Sat May 21, 2022 3:06 pm

I don't see that in 2.16.9 - just created a short encrypted SMPTE DCP, created a discrete (file) DKDM for DCP-o-matic, and was able to play that DCP in player after I assigned that DKDM. Will now try 2.16.10...

Carsten · Post by **Carsten** » Sat May 21, 2022 3:26 pm

Hmm, interesting, both main and player 2.16.10 crash hard right after start on my Mac OS Sierra system. 2.16.9 is okay. Now trying 2.16.11...
Same with 2.16.11. 2.16.9 still okay. Now with trashed prefs...

2.16.10 and 2.16.11 start ok after I trashed prefs. However, with trashed prefs, I can not test decryption of the encrypted DCP created with 2.16.9.

Will create a new one now with fresh prefs.

Okay - it works with 2.16.10 with fresh prefs for me. But maybe there is some prefs inconsistency that causes the crashes for me, and prevents decryption for you. Can you save/archive your prefs folder and start from scratch for a test? You may later need to save/restore your existing encryption/decryption chain if you want to keep your cert chain consistent with your earlier prefs/chain.

I usually just ZIP the prefs folder and add some meaningful name to it.

nimes · Post by **nimes** » Sat May 21, 2022 3:42 pm

I'm on Windows 10, DoM 2.16.10 runs properly except it gives an error while adding or playing encrypted DCPs.

Carsten · Post by **Carsten** » Sat May 21, 2022 3:44 pm

Maybe Carl needs to look into some prefs issue between 2.16.9 and 2.16.10

What does the error msg say?

nimes · Post by **nimes** » Sat May 21, 2022 3:45 pm

Right now I've returned back to 2.16.8 and is running perfectly. Won't be taking risk right now by trashing pref, because I've yet to generate KDM's for the film to be released this Friday. Thanks for the support Carsten, will be testing it on the next system.

nimes · Post by **nimes** » Sat May 21, 2022 4:00 pm

This is the error message after trying to play or import encrypted DCP in 2.16.10

Post by **carl** » Sat May 21, 2022 7:43 pm

I'm seeing this here now, thanks - I'll look into it. Here's a bug report.

Post by **carl** » Sat May 21, 2022 8:25 pm

A fix is in the works; I just need to run the tests and then build - should be uploaded within the next 24 hours or so.

Post by **carl** » Sat May 21, 2022 10:35 pm

2.16.10 and 2.16.11 start ok after I trashed prefs. However, with trashed prefs, I can not test decryption of the encrypted DCP created with 2.16.9.

Did you choose OpenGL mode again after trashing the prefs? Maybe I broke the OpenGL backend?

DCP-o-matic

2.16.10 Can't open encrypted DCP

2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP

Re: 2.16.10 Can't open encrypted DCP