Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Content protection with UMS

212 views

Published on

A short talk about the content protection possibilities of our server stack

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Content protection with UMS

  1. 1. Content Protection in UMS (Ustream Media Server) Zoltán Németh Engineering Manager, Core Systems
  2. 2. at a glance Live streaming Free broadcastingSoftware as a Service Enterprise clients with protected content • Internal broadcasts • Copyrighted materials • Embed restrictions • Monetizing
  3. 3. Streaming
  4. 4. UMS  Ustream Media Server  Continuous connection to all clients  Real-time push-based updates  First use: viewer number display  Channel status poll  Viewer authentication and authorization  Stream information  Java, kernel tweaks
  5. 5. UMS  The source of all information for streaming clients  Communication over RTMP / Websocket / HTTP  Secure is also available (WSS, HTTPS)  Current: Zorp  Next gen: own SSL termination  DNS balanced, multiple clusters
  6. 6. Broadcaster authentication  Upon connect, on the Ingest Server  Several methods  FMLE – like Channel Key  Ustream Session  Oauth  On fail  Reject  Allow but off air
  7. 7. Viewer authentication  UMS, on connect, based on Ustream session  Locks  Password  Email capture  Geo, IP  Referer (embed)  3rd party auth integrations  Reject on fail  Revalidate in real time on changes
  8. 8. Protecting the content on CDN  Basic: frequently changing live URL  Shared secret based hash  Hash generated on UMS  Different hash for each viewer  Hash validated on Edge  Specific TTL  Lockhash – changes if locks are modified
  9. 9. Questions syntaxerror@ustream.tv

×