You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using nginx-rtmp for a while to convert and serve HLS streams. Recently I have been looking to upgrade this to use LLHLS and came across OvenMediaEngine and feel it is Avery viable upgrade for my use case.
I have been trying to wrap my head around various methods to secure this essentially closed loop secure video stream where I control both ends. I.e. I have an app to access an HLS (LLHLS) stream not for public consumption.
To help secure the stream, I know I can use TLS with login credentials to protect access to the stream but would like to also encrypt the stream in case the access is compromised. That led me down the DRM rabbit hole.
This is essentially for private use so going full bore on DRM is not really needed due to inherit costs. While researching, I see that you can encrypt segments using “basic” AES-128 with a url for the key. It does not appear that OvenMediiaEngine inherently supports this, but does have DRM?
I came across the Identity Key Format while reading up on DRM, and it appears to essentially be the fore-mentioned AES method.
Is this DRM format supported? It is not clear to me that it is. I see the info.xml file used for DRM requires several lines such as , , and values, but wasn’t sure if these can be formatted for the Identity type.
Any assistance or nudges to resources would be appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have been using nginx-rtmp for a while to convert and serve HLS streams. Recently I have been looking to upgrade this to use LLHLS and came across OvenMediaEngine and feel it is Avery viable upgrade for my use case.
I have been trying to wrap my head around various methods to secure this essentially closed loop secure video stream where I control both ends. I.e. I have an app to access an HLS (LLHLS) stream not for public consumption.
To help secure the stream, I know I can use TLS with login credentials to protect access to the stream but would like to also encrypt the stream in case the access is compromised. That led me down the DRM rabbit hole.
This is essentially for private use so going full bore on DRM is not really needed due to inherit costs. While researching, I see that you can encrypt segments using “basic” AES-128 with a url for the key. It does not appear that OvenMediiaEngine inherently supports this, but does have DRM?
I came across the Identity Key Format while reading up on DRM, and it appears to essentially be the fore-mentioned AES method.
Is this DRM format supported? It is not clear to me that it is. I see the info.xml file used for DRM requires several lines such as , , and values, but wasn’t sure if these can be formatted for the Identity type.
Any assistance or nudges to resources would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions