Hello, thanks a lot for your answers. I'm working with Carlo at the project and I'm sure we haven't explained our aim completely.
Essentially we would love to "protect" and encrypt the whole streaming chain end to end. We would like to stream RTMPS from our encoders (which should be authenticated and encrypted at the same time) and then transmux those streams into HLS and distribute those with encryption again (probably on an HTML5 page via HTTPS). Since our content is very sensible we really need to have encryption all the way. Also probably we will need DRM (but that's something we'll understand further down the line).
So the questions are:
Is there any way to push RTMPS and RTSPS streams on nimble?
If so, where and what are the options to use them? (we don't seem to find an interface for those)
Do we need to use TLS v1.3 (v stands for version) certificates to stream RTMPS and RTSPS on nimble?
Also, I know this is not a question related to Nimble Streamer but we are quite new to the streaming world, what key are RTMPS and RTSPS using to encrypt the streams?
Are they using the username and password to generate the encryption? Or do we need a kind of certificate on the encoder side to properly encrypt those streams?
Thanks a lot for your help