Skip to main content
May 18, 2015
Question

How to generate vodkey.bin for (P)HLS

  • May 18, 2015
  • 0 replies
  • 665 views

Hello,

how are the vodkey.bin-files in the ams_hlskeys-directory generated? On-the-fly by the AMS? I just don't get it from the documentation (https://helpx.adobe.com/adobe-media-server/dev/configuring-content-protection-hls.html#serve_encryption_keys_to_the_client)...

My config looks like this:


<Location /hls-vod>

            HLSHttpStreamingEnabled true

            HLSMediaFileDuration 8000

            HttpStreamingContentPath "/web/ntvori/fms_data"

            HLSFmsDirPath "/opt/adobe/ams_origin"

            HLSJITConfAllowed true

            ########################################

            # Cache-control header configuration start

            # Specify the max-age(in secs) to set in the Cache-Control header

            # for different response types (m3u8, ts, drmmeta,...).

            # A value of -1 turns off setting the cache control header.

            HLSM3U8MaxAge 86400

            HLSTSSegmentMaxAge 86400

            HLSMetaMaxAge 3600

            # Cache-control header configuration end

            ########################################

            # Uncomment the following directives to enable encryption

            # for this location.

            #    HLSEncryptionScope server

            #    HLSEncryptCipherKeyFile "../creds/vodkey.bin"

            #    HLSEncryptKeyURI        "https://<ServerName>/hls-key/vodkey.bin"     <-- Should I here just uncomment and everything is fine???

            Options -Indexes FollowSymLinks

        </Location>

Or do I need the "hls-vod-enc-key"-module?

<Location /hls-vod-enc-key>

           HLSEncryptHostCipherKey true

           HLSFmsDirPath "/opt/adobe/ams_origin"

           HLSEncryptKeyRepository "/web/blabla/fms_data/ams_hlskeys"

           #SSLRequireSSL

           #SSLRequire %{SSL_CLIENT_S_DN_CN} eq "iPhoneOS Device Certificate"

        </Location>

Thanks in advance!

Regards, Sven


This topic has been closed for replies.