Unauthenticated RTMP port connections can "start" a stream
SceneCityDev opened this issue · 2 comments
SceneCityDev commented
Exploit scanners hitting port 1935 can cause this:
[2024-04-06 12:44:12.584] I [SPRTMP-t1935:977208] Provider | stream.cpp:51 | Unknown/(105) has been started stream
[2024-04-06 12:44:12.585] I [SPRTMP-t1935:977208] RTMPProvider | rtmp_provider.cpp:194 | A RTMP client has connected from <ClientSocket: 0x7f1e67401210, #35, Connected, TCP, Nonblocking, 139.99.238.162:54674>
My RTMP port is protected with SignedPolicy of course. Maybe the log message is just wrong, but how can someone sending random data to port 1935 cause a stream to start?
getroot commented
This does not mean that the RTMP stream has started, but simply indicates that someone has connected to the RTMP port, which is still in the Unknown state. (Before negotiation)
getroot commented
I am closing this issue because I don't think it is a problem. If I misunderstood this, please reopen the issue.