Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unauthenticated RTMP port connections can "start" a stream #1596

Closed
SceneCityDev opened this issue Apr 7, 2024 · 2 comments
Closed

Unauthenticated RTMP port connections can "start" a stream #1596

SceneCityDev opened this issue Apr 7, 2024 · 2 comments

Comments

@SceneCityDev
Copy link

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
Copy link
Sponsor Member

getroot commented Apr 8, 2024

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
Copy link
Sponsor Member

getroot commented Jun 3, 2024

I am closing this issue because I don't think it is a problem. If I misunderstood this, please reopen the issue.

@getroot getroot closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants