Invalid CPL signature on Barco

[Carsten]

Yup, there is an issue. Barco ICMP is on 1.4.3.7.

I tried first with 2.14.57 on our cinema windows machine, with an encrypted SMPTE DCP. Ingest of both DCP and KDM, no issues, Barco properties dialog says: 'Valid, OK to play', and it does indeed play.

Then I tried it with 2.15.171, which I still have on my Mac. I created an encrypted SMPTE DCP and set all necessary metadata, basically, all language to DE. Barco ingested DCP and KDM fine, properties dialog says 'Valid, Ok to play' - but when I try to play, I get this error:

Bildschirmfoto 2022-02-03 um 04.50.18.png

As a first try, I can make both DCPs (2.14.57 and 2.15.171) available to you, they are small. Both do work in DCP-o-matic player 2.15.180 with local selfDKDMs, the one done with 2.15.171 get's no validator complaints. I can also try to generate a KDM towards our Sony and try it there. I may get a chance to access another ICMP on Monday which I can/will update to the most recent software version.

[StephW999]

hi carl,
Maybe it's a problem with the version of openSSL which produces a wrong cipher value string, or because of a newer version of libxmlsec.

[carl]

Great - that's the same error as the other reporter was seeing. If I can compare the good and bad DCPs that would be a good start. If there's nothing obvious from there we might have to go back through 2.15.x to work out where it was introduced.

[carl]

Here's the bug

[carl]

I guess if you have time it would also be interesting to try the latest test version just in case this is caused by the empty AnnotationText tags for some bizarre reason.

I could just about imagine the signer code discarding the empty tag before signing, or something.

The latest test is called 2.16.0 as I just got it all prepared for release on Monday

[Carsten]

I added dropbox links to the two DCPs on Mantis.

I COULD update the Barco to the very latest version, but I would not do it immediately. Nothing in the recent Barco version history says something that could be relevant to this problem. But very often 'smaller' bugs simply are not mentioned there and are cleaned out silently.

I am now creating another DCP with the most current test release, using the same project file and settings.

[Carsten]

Same problem with 2.16.0

Bildschirmfoto 2022-02-03 um 18.56.09.png

[Carsten]

BTW - I tried to play all three (2.14.57/2.15.171/2.16.0) encrypted DCPs on our Sony - but when ingesting the KDMs, those created with 2.15.171 and 2.16.0 are rejected as invalid (no further details). I am quite sure I did everything right, but will try to recreate these DCPs and KDMs again later.

The encrypted DCP and KDM created with 2.14.57 ingest and play okay on both the Barco and the Sony.


Carl - I can't find the 'empty AnnotationText tags' bug on Mantis in the 'Resolved' bug list - do you have a link?

[carl]

The other Sony bug is here.

[carl]

BTW - I tried to play all three (2.14.57/2.15.171/2.16.0) encrypted DCPs on our Sony - but when ingesting the KDMs, those created with 2.15.171 and 2.16.0 are rejected as invalid (no further details). I am quite sure I did everything right, but will try to recreate these DCPs and KDMs again later.

Oh dear - maybe you're seeing the other mystery Sony bug. I'll look at your links as soon as I can and see if anything is obvious.