Posts: 4

Topic: Encryption Key and KeyID Are The Same In MXF

I've been playing around with using OpenDCP to make encrypted SMPTE MXFs, and have found that the package uses the Key ID field for both the Key and Key ID. This results in a track file that doesn't use the intended key, and more problematic, that the actual key is published in the Key ID.

I initially hoped that they were swapped, but it just looks like the same Key ID field is used for both value pairs. Obviously this would be a real problem in protecting content.

You can verify this by making an encrypted MXF and using asdcp-unwrap -k to confirm which fields were used. Additionally, you can get the MXF's Key ID field by using asdcp-info -H test.mxf and looking for the "CryptographicKeyID = " field.

Thanks again for all your hard effort, it would be great to be able to use this package for encrypted asset creation!