Roku Developer Program

[dootv]

Hello

We are currently building a new public channel that has many changes daily. We have thousands of episodes and several dozen that changes daily. We are using grid that calls out on xml files to pull VOD HLS stream from Wowza. We want to encrypt that communication between Roku and our Wowza along with our XML. The XML are actually being hosted on a web server. The reason behind it is we update several dozen of changes on the XML’s daily.

What recommendation and alternative solution with updating our episodes without using XML if that is even possible? How can we encrypt the communication from Roku to XML file and then Roku to Wowza? Any other alternative solutions?

Thanks in advance!

[dootv]

Currently, Wireshark will capture our Roku communicating with our xml file and people are able to access our stream directly from our XML.

[bandal]

But, consider how many will attempt to use WS and if so, how will they know the names of the other video content you want to protect. Unless the naming convention is easy to guess. Maybe about less than 2% will be hackers. Maybe not worth worrying about. Just my opinion.

[dootv]

Our live streams is exposed on XML. Any site can leeach off of our live stream. That includes all of our competitors.

[RokuJoel]

Hiding your XML is no sweat, just use SSL to retrieve the XML. It should be possible to use SSL for playback of your content as well, there are various threads on this here in the forum.

- Joel

[TheEndless]

Any reason you can't use AES encryption for your HLS stream? If you're genuinely concerned about leaching and/or your competitors stealing your streams, that's probably your best bet to prevent it.

[destruk]

Anything you decide to use could be cracked, even SSL. http://www.google.com/search?q=ssl+cracked
If you require true security, the internet isn't the way to do it.
Do you actually think your content is the holy grail that everyone on the planet is looking for to require ironclad protection? LOL... gee, I wonder what it is. Wikileaks videos perhaps?

[destruk]

I'm just saying, protection options are available like SSL, as well as many other encryption and authentication possibilities for you to use, but if you think using anything or all of them will make your content 100% secure from a threat, nothing will. Worst case is someone sets up a camcorder and records the tv screen during playback in their own home, or records it using composite cables or bypassing the HDCP. http://hackaday.com/2009/10/01/tv-hack-bypasses-hdcp/
If it makes you sleep better knowing that you have used every available protection feature, that's why they are there, but it will not keep your content protected from everything.

[RokuMarkn]

The OP did not state that he expected 100% protection for his content. He was just asking for recommendations for protection options. Almost every Roku channel puts some form of protection on their content. This is entirely reasonable and does not merit the attacking responses in this thread. If you don't have any constructive suggestions to offer to the OP, please refrain from posting.

--Mark

[dootv]

Thanks for all the great suggestion. It would be good enough for us just to hide where Roku is pulling the XML files. Our XML files basically will list all our content and streams that we do not want our competitors to see. We have tried using SSL our Roku which would call a (https://webserver/ourxmlfile.xml) but it will not load. Our certificate shows OK within our web browsers such as Google Chrome and IE 8-10 on our webserver. Do we have to load our app with our SSL cert?

We want to Roku to call our https://webserver/ourxmlfile.xml so it is at least hidden from WireShark Capture.

Thanks in advance!