Roku Developer Program

[Xerces77]

The vids for my channel are hosted on an Apache web server. My hosting provider stated they recently made an update to SSL on the server in response to this:

http://arstechnica.com/security/2012/09 ... erts-warn/

It's something to do with SSL Compression on Apache Servers that's on by default. My channel has been working flawlessly up to last weekend (Oct 27/28). I've contacted them and they say they want to reproduce the error but they do not have access to a Roku!

WHAT CAN I DO ALL THE VIDS ON MY CHANNEL ARE NO LONGER ACCESSIBLE! I GET THE FOLLOWING ON MY ROKU WHEN TRYING TO ACCESS VIDS:

http error: -1 URL: https://<myURL>/radio/chat/chat.mp4
showVideoScreen | msg = An unexpected problem (but not server timeout or HTTP error) has been detected. | index = -3
Video request failure: -3 0
showVideoScreen | msg = | index = 0

[destruk]

Aside from sending them a $40 roku device?

[Xerces77]

Admins (or Roku personnel)

I have an update from my hosting provider regarding encryption. Please send me a private message where I can reply discreetly.

[Xerces77]

Greetings -

I've sent private messages to the person who replied to my last post. I need the level of AES encryption the Roku is compatible with (128bit, 256bit, or both)

-Xerces77

[destruk]

You also need the SDK/wiki link since it contains that information --

aes-[128|192|256]-cbc 128/192/256 bit AES in CBC mode
aes-[128|192|256] Alias for aes-[128|192|256]-cbc
aes-[128|192|256]-cfb 128/192/256 bit AES in 128 bit CFB mode
aes-[128|192|256]-cfb1 128/192/256 bit AES in 1 bit CFB mode
aes-[128|192|256]-cfb8 128/192/256 bit AES in 8 bit CFB mode
aes-[128|192|256]-ecb 128/192/256 bit AES in ECB mode
aes-[128|192|256]-ofb 128/192/256 bit AES in OFB mode

http://sdkdocs.roku.com/display/RokuSDKv48/roEVPCipher

For HLS - a quick search of the wiki site also states -

4.1 Encryption
Section 6.2.3 of the HLS specification gives details about the AES 128 bit encryption that HLS can use to protect your content. The Apple tools above can also be used to encrypt your segments. Here are the same commands adding encryption:
% mediafilesegmenter –b http://yourhost.com/segmentsDirectory -t 10 \
-l -i playlist3200.m3u8 –f ~/OneTransportStreamFile3200.ts –K \ https://yourhost.com/keyURL -J random
The –K option lets you specify the URL to use for the encryption key. You will want to protect access to the key, and a good authentication scheme is necessary. Please see the security write-up about client certificates and mutual authentication SSL in the Component Reference roUrlTransfer writeup. The –J command specifies a random IV (Initialization Value) for each segment's encryption. The IV value for each segment is included in the .m3u8 file. The same –K and –J options can be added to the other two mediafilesegmenter commands. The variantplaylistcreater command remains the same.

[Xerces77]

Thanks for your assistance.

Roku admins- I've enabled AES 128-bit on my web host and vids are still getting the same error!!!!

[Xerces77]

It's definitely an issue with SSL. When I reverted to URLs without https, my vids worked fine. My code's roVideoScreen object is using the default crt bundle (screen.SetCertificatesFile("common:/certs/ca-bundle.crt"))

but this no longer works as it may no longer be valid. I've browsed other threads and saw one where the ROku could not view HLS over HTTPS. The roku rep responded with some kind of fix where all the .crt files on the web server were placed into one and a function SetCertificatesDepth was called but this isn't even in the SDK documentation with the version of the Roku I have.

Could a Roku Tech support person please respond?????

[Anonymous]

What cipher are you using? Please email details and a sample URL to developer@roku.com