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
OvenMediaEngine currently supports SRT encryption only via a globally
configured passphrase in Server.xml (SRTO_PASSPHRASE). This means all
SRT publishers connecting to the same OME instance share the same
pre-shared key.
For multi-tenant deployments with many independent publishers, this
creates a shared-secret problem: if one publisher's client is
compromised, the encryption key for all SRT streams on that OME
instance is exposed.
Current behavior
SRT passphrase is static, defined in Server.xml
All publishers share the same passphrase
Admission Webhooks can authenticate publishers per-stream ✅
But stream-level encryption remains global ❌
Desired behavior
Allow OME to apply a per-stream passphrase for SRT encryption,
provided dynamically by the Admission Webhook control server response.
Proposed approach: Extend the Admission Webhook response to include
an optional passphrase field:
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.
Uh oh!
There was an error while loading. Please reload this page.
Problem
OvenMediaEngine currently supports SRT encryption only via a globally
configured passphrase in
Server.xml(SRTO_PASSPHRASE). This means allSRT publishers connecting to the same OME instance share the same
pre-shared key.
For multi-tenant deployments with many independent publishers, this
creates a shared-secret problem: if one publisher's client is
compromised, the encryption key for all SRT streams on that OME
instance is exposed.
Current behavior
Server.xmlDesired behavior
Allow OME to apply a per-stream passphrase for SRT encryption,
provided dynamically by the Admission Webhook control server response.
Proposed approach: Extend the Admission Webhook response to include
an optional
passphrasefield:{ "allowed": true, "lifetime": 60000, "srt": { "passphrase": "<per-stream-key>", "pbkeylen": 16 } }****All reactions