Protection for incoming streams

Hi!

I test nimble streamer.

I need accept only incoming stream from created applications, as wowza does.

Actually any publishers can push any streams to my server through the specified port.

Try to follow this guide, but still anyone can send signal to my server:

http://blog.wmspanel.com/2015/10/rtsp-publish-control-framework-overview.html

Thanks

Sorry, anyone is a error word (I use google traslate).

All people can send signal to my server when nimble is running, I need solve this.

Please check
http://blog.wmspanel.com/2014/06/rtmp-hls-transmuxing.html
if you need to setup publish password please fill Push Login/Push password in "Global" settings so nobody without password can push.
In addition you can setup per Application login/password.

sure, but we are a streaming provider. If we use the push password, it would be the same for all clients. Upon termination of a client, the client could continue to log in with the global password. What I need, is to only accept the incoming stream of the applications that I activate. And when you delete an application, it can not continue to connect.

Hello Gabriel.
You can set up publish control with signature (you will need to generate signature for client and put it in publish URL) or authorization handler (providing authentication procedure on your own server). These procedures are described in http://blog.wmspanel.com/2015/12/rtsp-publish-control-setup.html in "Using publish signature" and "Using publish authorization handler" sections.

And it is.

But the password is only for the application that I configure.

Anyone can send signal to the server, in other applications.

Maybe there is something I am not understanding well. I apologize.

What I need is that they can only send signals to the server, in the applications that I activate.

As in wowza, it only receives signal when I create the application.

Hi,
1)you should specify random login and password in Nimble Streamer->Live Streams Settings->Global. This way your users will not be able to publish streams to "nonexistent" application.
2)if you can create separate application settings for all your clients just create application for every client and specify exact password. Please note that if you delete application after that this will block new publishing request but currently publishing streams will work till restart
3)if you need ability to block any stream during publishing you need to setup "Publish control" from "Control"->"Publish control" menu. You need to specify unique password for each application and specify your handler as well.

Please note that to prevent unauthorized publishing you need to specify "Nimble Streamer->Live Streams Settings->Global->Login|Password" in anyway. If you don't anyone can publish to our server using any application name. Nimble and Wowza works differently. When you setup Nimble don't use experience you had with another media server.

Thank you

Yes, but if I specify "push login" and "push password" (in live stream settings -> Global), all my clients must use same user and password to connect.

Anyone who has that user and password, will be able to connect without my authorization.

I need only accept incoming stream for autorized users (applications).

Thanks

For example in Wowza is:

<Property>
<Name>limitPublishedStreamBandwidthMaxBitrate</Name>
<Value>1300</Value>
<Type>Integer</Type>
</Property>

Solved another question (protect incoming stream)

Thank you!

Hi Gabriel
Sorry for delay.
There is a method to limit bitrate, but it pretty complicated.
You must follow procedure decribed at "Controlling streaming process" section in http://blog.wmspanel.com/2015/12/rtsp-publish-control-setup.html

First, you will need to enable management API on you Nimble instance, as it described here:
https://wmspanel.com/nimble/api#toggler=0 and http://blog.wmspanel.com/p/nimble-streamer-configuration.html
In a brief: add line "management_listen_interfaces = 127.0.0.1" in /etc/nimble/nimble.conf file and you can send management requests to port 8082 from same host.
Then you should create some serivice that will periodically repeat following steps:
1) Get URL http://127.0.0.1:8082/manage/rtmp_status for a list of opened streams. Sample response:
[{"app":"live","streams":[{"strm":"one","publish_time":"1507804598","bandwidth":"630820","resolution":"424x240","vcodec":"avc1.42c01e","acodec":"mp4a.40.2","protocol":"RTMP"},{"strm":"two","publish_time":"1507804448","bandwidth":"125340","resolution":"1200x720","vcodec":"avc1.42c015","acodec":"mp4a.40.2","protocol":"ENCODER"}]}]
2) Get list of streams with ID's with http://127.0.0.1:8082/manage/publish_control/status . Sample response:
{"PublishControlStatus":[{"key":"1", "id":"ID_1", "ip":"192.168.1.1","stream":"live/one"}, {"key":"2", "id":"ID_2", "ip":"192.168.1.2","stream":"live/two"}]}
3) Match streams from rtmp_status with streams from publish_control/status and do POST list of clients you want to deny to
http://127.0.0.1:8082/manage/publish_control/deny . Sample request:
{"PublishControlDenyRequest":["2"]}

Of course, it's not simple.

There should be some easy method to set the maximum bitrate of a stream.

It's basic.

Any simpler alternative? At least to set a default value for all streams.

No, it's the only one way

Will it be available in a future update?

You can do what you need following provided method. You will get simple script with your business logic and you will probably even like you can control your publisher completely implementing any logic you want.

We don't have any plans to implement it in the way you propose. This doen't mean we will not. This doesn't mean we will though.
We got nothing to say more on the subject. If you want to have it now you already got reply.