DVS Clipster Specifications download pdf (Page 43)

6-11

Miscellaneous

public key of the Encryption Key. Afterwards the encrypted AES keys

are written to the KDM file. Of each encrypted track file a hash value

is created which is then written to the PKL file. Next, the completed

CPL, KDM and PKL are signed with the Signing Key. The finished DCP

can then be sent to the Recipient.

The Keys at the Recipient

This diagram shows the keys as they are applied at the Recipient’s site:

Figure 6-4: The keys and where they are used on the Recipient side

At the Recipient the received DCP has to be validated with the help of

the public Signing Key that is attached to each extra file of the DCP

(e.g. CPL, KDM or PKL). Whether the track files were received unmod-

ified can be checked by comparing the hash values written in the vali-

dated (and thus unaltered) PKL file with hashs calculated from the

received track files. The completely validated DCP can then be played

Track File

Creator

Certificate

AES Key

Encryption Key

(private of Reci-

pient Certificate)

Signing

Key

(public)

decrypt

compare

validate

AES encrypted

Track File

RSA encrypted

AES Key

Hash Hash

Recipient

D-Cinema Player

DCP

KDMCPL PKL

Validated

1 2 ... 38 39 40 41 42 43 44 45 46 47 48 49

No comments

DVS Clipster Specifications Page 43