[camillo]

I am trying to use mxfcrypt but:

- the binary just tells me that there is no LIBEAY32.dll
if I put in the DLL taken from the web it says there is no number 3... and stuff like that.

- if I compile the project with VS2003 it says I am missing the libeay.lib

What can I do?
Can you upload the right DLLs to work with mxfcrypt or can you tell me how to compile it?

Thank you very much.

PS Just a question: if I encrypt an MXF what would I have to expect for example from WindowsMediaPlayer trying to open & play it?

Regards,
Camillo

[Matt Beard]

Oops - looks like the release copy was built to require the OpenSSL DLL to be on your machine (it is one of those DLLs that gets installed by many programs so is often there). This seems to have been caused by a new directory layout in the latest versions of OpenSSL for Windows.

The required DLL is the one from OpenSSL version 0.9.8d.

I will build a non-DLL version and add it to SourceForge in place of the existing one.

If you want to build it yourself you need to install OpenSSL and set environment variable OPENSSL_ROOT to its directory.

[camillo]

Thank you very much!
Can you tell me when you preview this new version to be updated?

Thanks!

Camillo

[Matt Beard]

It is now available from the SourceForge project page.

Sorry about the delay - spend a few days with major network and PC problems!!

[camillo]

Man you are great!

I tried to crypt an MXF file and play with WindowsMediaPlayer 9... the player crashes!!!

How powerful the crypting algorythm!
I was expecting a more soft message, but maybe in the future...

Thanks!

Regards,
Camillo

[Matt Beard]

Wow! A feature that can make a Microsoft application crash!

</sarcasm>

[camillo]

Please, some technical questions:

- In the mxfcrypt or encryption module of freemxf library, do you use the SMPTE 429-6-2006: D-Cinema Packaging — MXF Track File Essence Encryption standard?

- What kind of algorithm do you use? I mean, it is a proprietary algorithm or if I take some third party decrypter, I insert my public key and the decryption is done? Is there a standard algorithm?

Thank you!

Regards,
Camillo

[Matt Beard]

Yes the encryption is done as per 429-6. Note that this is only the essence encryption and does not include any of the key delivery or packaging that the full dc28 system uses.

The algorithm used is AES-CBC with a 128-bit key. An optional HMAC-SHA1 packet can be added to each essence KLV to verify integrity of the essence.

The encryption and decryption are handled by the openssl library, but this could easily be swapped for any other compliant AES codec.

The files should be able to be decrypted by other 429-6 compliant decoders (as long as they are happy to accept a single track-file and a raw key) and the code has been shown to be able to decrypt files produced by other encoders.