Managing AES encryption for SST outputs
When distributing content from your own StreamHub to a third party StreamHub, you may not want to share the AES key used to encrypt your input streams. In that case, you can disable AES encryption for a given SST output or specifying a dedicated AES encryption key for this output.
The table below indicates which pairs of configuration are functional when coupling two StreamHub through SST.
It also gives which AES encryption configuration should be applied on the output profile from the source StreamHub interface (see Configuring IP Output Profiles).
Source StreamHub | ||||
No AES option with license | AES disabled | AES enabled | ||
Destination StreamHub | License without AES option | No dedicated configuration | On source StreamHub, AES key mode of output profile should be set on "global" or "disabled". | On source StreamHub, AES key mode of output profile should be set on "disabled". |
AES disabled | No dedicated configuration | On source StreamHub, AES key mode of output profile should be set on "global" or "disabled". | On source StreamHub, AES key mode of output profile should be set on "disabled". | |
AES enabled | Not supported | On source StreamHub, AES key mode of output profile should be set on "custom", using the destination AES key. | If source and destination StreamHub share the same key, AES key mode of output profile should be set on "global". If not, use the "custom" mode, entering and the destination AES key. |