Protected Streaming: Difference between revisions
←Created page with ''''Protected Streaming''' is a DRM-Technologie by Adobe. It is used to protect digital Content (Video or Audio) from unauthorized use. In fact, Protected Streaming...' |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Protected Streaming''' |
'''Protected Streaming''' |
||
is a DRM- |
is a DRM-Technology by Adobe. It is used to protect digital Content (Video or Audio) from unauthorized use. |
||
In fact, Protected Streaming consists of many different techniques; basically there are two main components: |
In fact, Protected Streaming consists of many different techniques; basically there are two main components: |
||
| Line 30: | Line 30: | ||
to avoid that manipulated clients can access the content. Those clients could possibly write the unencrypted content to a file. |
to avoid that manipulated clients can access the content. Those clients could possibly write the unencrypted content to a file. |
||
Besides that, it ist possible to restrict connections to the Flash Media Server to a list of known hosts, to avoid that the whole player (the flash client) |
Besides that, it ist possible to restrict connections to the Flash Media Server to a list of known hosts, to avoid that the whole player (the flash client) is placed on a foreign site. |
||
is placed on a foreign site. |
|||
Revision as of 16:00, 6 November 2008
Protected Streaming is a DRM-Technology by Adobe. It is used to protect digital Content (Video or Audio) from unauthorized use.
In fact, Protected Streaming consists of many different techniques; basically there are two main components:
Encryption:
All contents are encrypted by the Flash Media Server "on the fly". This means, there is no encryption of the source file needed (which is different to Microsoft DRM, for instance). For data transmission, a special protocol is used: rtmpe or rtmps.
rtmps uses SSL-encryption, rtmpe makes use of proprietary encryption algorithms. rtmpe causes less CPU-load than rtmps on the Flash Media Server, but the encryption has been hacked: There are existing tools to decrypt rtmpe streams and save the content unencrypted to a file.
Currently, there are no known hacks for rtmps and also there are no known tools to perform rtmps decryption. rtmps takes more CPU-ressources server-side, than rtmpe.
SWF-Verification
This technique is used to ensure that only the official Flash Client, delivered by the content owner, can be used to request the streaming data.
All officially allowed clients (which are in fact *.swf Files), need to be placed on the Flash Media Server. Any unknown client requesting a connection, will receive an "connection reject".
The combination of both techniques ensures, that streams cannot be sniffed and stored into a local file. SWF Verification is needed,
to avoid that manipulated clients can access the content. Those clients could possibly write the unencrypted content to a file.
Besides that, it ist possible to restrict connections to the Flash Media Server to a list of known hosts, to avoid that the whole player (the flash client) is placed on a foreign site.