Microsoft Silverlight. The requirements in this section 9 only apply if the Microsoft Silverlight product is used to provide the Content Protection System.
Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” only apply if the Microsoft Silverlight product is used to provide the Content Protection System. Microsoft Silverlight is approved for streaming if using Silverlight 4 or later version. Apple http live streaming The requirements in this section “Apple http live streaming” only apply if Apple http live streaming is used to provide the Content Protection System. Licensee shall migrate from use of the Apple-provisioned key management and storage for http live streaming (“HLS”) (implementations of which are not governed by any compliance and robustness rules nor any legal framework ensuring implementations meet these rules) to use (for the protection of keys used to encrypt HLS streams) of an industry accepted DRM or secure streaming method which is governed by compliance and robustness rules and an associated legal framework, within a mutually agreed timeframe. Http live streaming on iOS devices may be implemented either using applications or using the provisioned Safari browser. The URL from which the m3u8 manifest file is requested shall be unique to each requesting client. The m3u8 manifest file shall only be delivered to requesting clients/applications that have been authenticated in some way as being an authorized client/application. The streams shall be encrypted using AES-128 encryption (that is, the METHOD for EXT-X-KEY shall be ‘AES-128’). The content encryption key shall be delivered via SSL (i.e. the URI for EXT-X-KEY, the URL used to request the content encryption key, shall be a https URL). Output of the stream from the receiving device shall not be permitted unless this is explicitly allowed elsewhere in the schedule. No APIs that permit stream output shall be used in applications (where applications are used). The client shall NOT cache streamed media for later replay (i.e. EXT-X-ALLOW-CACHE shall be set to ‘NO’). iOS implementations (either applications or implementations using Safari and Quicktime) of http live streaming shall use APIs within Safari or Quicktime for delivery and display of content to the greatest possible extent. That is, implementations shall NOT contain implementations of http live streaming, decryption, de-compression etc but shall use the provisioned iOS APIs to perform these functions. iOS applications, where used, shall follow all relevant Apple developer best practices and shall by this method or otherwise ensure the applications are as secure and robust as poss...
Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” only apply if the Microsoft Silverlight product is used to provide the Content Protection System. Microsoft Silverlight is approved for streaming if using Silverlight 4 or later version.
Microsoft Silverlight. The requirements in this section “Microsoft Silverlight” only apply if the Microsoft Silverlight product is used to provide the Content Protection System. Microsoft Silverlight is approved for streaming if using Silverlight 4 or later version. Security updates Licensee shall have a policy which ensures that clients and servers of the Content Protection System are promptly and securely updated in the event of a security breach (that can be rectified using a remote update) being found in the Content Protection System and/or its implementations in clients and servers. Licensee shall have a policy which ensures that clients and servers of the Content Protection System are promptly and securely updated with updates received from the provider of the Content Protection System. Filtering Licensor Content from Un-trusted Sources The Licensed Service shall make best efforts to prevent the unauthorized delivery and distribution of Licensor’s content from un-trusted sources (for example, user-generated / user-uploaded content) using an approved filtering technology.
Microsoft Silverlight. The requirements in this section 9 only apply if the Microsoft Silverlight product is used to provide the Content Protection System. Microsoft Silverlight is approved for streaming if using Silverlight 2 or later version. When used as part of a streaming service only (with no download), Playready licenses shall only be of the the SimpleNonPersistent license class. Within 6 months of the commercial launch of Silverlight 4, Licensee shall migrate to Silverlight 4 and be in full compliance with all content protection provisions herein or;. Within 6 months of the commercial launch of Silverlight 4, Licensee shall migrate to alternative, Licensor-approved DRM/streaming protection technology in full compliance with content protection requirements herein. Protection Against Hacking The following requirements shall be supported on (i) the Licensed Cable Service system used to protect Licensed Content; and (ii) the Licensed Internet Service Flash Access 2.0, once such upgrade has been completed, to protect Licensed Content: [Xxxxxx: Need to discuss why this section cannot apply to the Internet Service when using RTMP-E?] Playback licenses, revocation certificates, and security-critical data shall be cryptographically protected against tampering, forging, and spoofing. The Content Protection System shall employ industry accepted tamper-resistant technology on hardware and software components (e.g., technology to prevent such hacks as a clock rollback, spoofing, use of common debugging tools, and intercepting unencrypted content in memory buffers). Licensor acknowledges that the approved Content Protection System for the Licensed Cable Service is a proprietary system which is owned and controlled by Scientific Atlanta for the Province of Ontario and Motorola for the Atlantic Provinces. Each vendor’s tamper-resistant technology within the hardware and software components is not within the public domain. Licensor deems the conditional access systems of Scientific Atlanta and Motorola to comply with the tamper resistant techniques outlined in subsection 9.4 below. [TJW: can we accept this system for early window content?] The Content Protection System shall be designed, as far as is commercially and technically reasonable, to be resistant to “break once, break everywhere” attacks. The Content Protection System shall employ tamper-resistant software. Examples of tamper resistant software techniques include, without limitation: Code and data obfuscation: The executable bi...
