Skip to main content
Version: 4.0 (Archived) 📦

DRM

DRM use to protect the content, can use many strategys:

  • Referer Anti-suck: Check the referer(PageUrl) of RTMP connect params, which is set by flash player.
  • Token Authentication: Check the token of RTMP connect params, SRS can use http-callback to verify the token.
  • FMS token tranverse: Edge server will verify each connection on origin server.
  • Access Server: Adobe Access Server.
  • Publish Authentication: The authentication protocol for publish.

Referer Anti-suck​

SRS support config the referer to anti-suck.

When play RTMP url, adobe flash player will send the page url in the connect params PageUrl, which is cannot changed by as code, server can check the web page url to ensure the user is ok.

While user use client application, the PageUrl can be any value, for example, use srs-librtmp to play RTMP url, the Referer anti-suck is not work.

To config the referer anti-suck in srs:

# the vhost for anti-suck.
vhost refer.anti_suck.com {
# refer hotlink-denial.
refer {
# whether enable the refer hotlink-denial.
# default: off.
enabled on;
# the common refer for play and publish.
# if the page url of client not in the refer, access denied.
# if not specified this field, allow all.
# default: not specified.
all github.com github.io;
# refer for publish clients specified.
# the common refer is not overrided by this.
# if not specified this field, allow all.
# default: not specified.
publish github.com github.io;
# refer for play clients specified.
# the common refer is not overrided by this.
# if not specified this field, allow all.
# default: not specified.
play github.com github.io;
}
}

Remark: SRS3 use new style config for referer, which is compatible with SRS1/2.

The bellow protocols support referer:

  • RTMP: Both publisher and player.

Token Authentication​

The token authentication similar to referer, but the token is put in the url, not in the args of connect:

rtmp://vhost/app/stream?token=xxxx
http://vhost/app/stream.flv?token=xxxx
http://vhost/app/stream.m3u8?token=xxxx
http://vhost/rtc/v1/whip/?app=live&stream=livestream&token=xxx
http://vhost/rtc/v1/whep/?app=live&stream=livestream&token=xxx

SRS will pass the token in the http-callback. read HTTP callback

Token is robust then referer, can specifies more params, for instance, the expire time. For example:

  1. When user access the web page, web application server can generate a token in the URL, for example, token = md5(time + id + salt + expire) = 88195f8943e5c944066725df2b1706f8
  2. The RTMP URL to publish is, for instance, rtmp://192.168.1.10/live/livestream?time=1402307089&expire=3600&token=88195f8943e5c944066725df2b1706f8
  3. Config the http callback of SRS on_publish http://127.0.0.1:8085/api/v1/streams; , read HTTP callback
  4. When user publishing stream, SRS will callback the url with token to verify, if invalid, the http callback can return none zero which indicates error.

Note: You're able to verify the play.

TokenTraverse​

The FMS token tranverse is when user connect to edge server, the edge server will send the client info which contains token to origin server to verify. It seems that the token from client tranverse from edge to origin server.

FMS edge and origin use private protocol, use a connection to fetch data, another to transport the control message, for example, the token tranverse is a special command, @see https://github.com/ossrs/srs/issues/104

Recomment the token authentication to use http protocol; the token tranverse must use RTMP protocol, so many RTMP servers do not support the token tranverse.

SRS supports token tranverse like FMS, but SRS always create a new connection to verify the client info on origin server.

THe config for token tranverse, see edge.token.traverse.conf:

listen              1935;
vhost __defaultVhost__ {
cluster {
mode remote;
origin 127.0.0.1:19350;
token_traverse on;
}
}

Access Server​

SRS does not support.

Publish Authentication​

SRS does not support.

Winlin 2015.8