Describe the bug
Each connection to the server is counted as a "user"
Steps to Reproduce
telnet e.g. telnet example.org 64738Expected behavior
I expect something like nothing is changed in user counter (because is only TCP connection. ???it is not estabilished mumble control stream???)
Upd:
It is reproducible on Murmur 1.3.1 too.
This looks like the easiest way to DoS a murmur server.
I just tested next way:
telnet two timesServer connection rejected: Server is full (max 2 users). in my Mumble clientupd:
after some retries I got Global ban :D
Ignoring connection: ***MASKED IP*** (Global ban)
Is there a use-case for using a TCP-connection to the server without connecting to it? :thinking:
after some retries I got Global ban :D
That can be turned off in the server settings. It should only be a temporary ban though
It is question about legit usage of TCP conection??
Currently I using https://github.com/matteocorti/check_ssl_cert for checking ssl cert outdating
For my users it seems like periodicaly 1/100 users on server, but when someone join to server, they do not see anyone online.
It is question about legit usage of TCP conection??
Ah so the TCP connection doesn't have to talk to the mumble server for it to be counted as a User? Okay now I see the problem :bulb:
Yeah, user count should reflect accepted Mumble connections count. Not TCP connection count.
I do not looking deep in the code, but found interesting thing
We can have a problem with this, because session ids pool also dependent on iMaxUsers