Enable Secure Content clients to use their own content encryption key

[feliperoos]

Hi!

As of today, clients of the secure content specification cannot specify their own key to encrypt the content resources. That mechanism is today handled entirely by the library, on the account that we control the security by using the specified random generator callbacks. Although accepting the key from the client can weaken the encryption process, such case has been proved a valid use case in our context.