mumble-voip/mumble

[Feature Request] Allow disabling server connections to unregistered users

Open

#7176 opened on Apr 25, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (5,642 stars) (1,062 forks)batch import
aclfeature-requestgood first issueserver

Description

Context

I have a private server that I am only using with a specific group of friends. As all of us are registered in the server, I'd prefer if I could disable connections to the server to unregistered users. For now I'm stuck with setting a very long random password.

Description

I'd like for a configuration option to be introduced that denied all unregistered users from connecting, even with the password, to improve the security of the server from brute force attacks.

Mumble component

Server

OS-specific?

No

Additional information

It would also be great if this could be toggled while the server is running, for example to allow a new member to connect/register without having to restart the server, but I understand if this would be difficult to implement. This could also be introduced with one time passwords (issue #6061 talks about them).

Contributor guide

Tech stack
cpp
Domain
backendsecurity
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Mumble server codebaseBasic knowledge of C++Understanding of configuration options in Mumble
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The feature request asks for a configuration option to deny connections from unregistered users. Key files to examine are likely in the server configuration handling (e.g., ServerConfig.cpp or similar) and the authentication/connection logic (e.g., Server.cpp or Connection.cpp). The issue references #6061 for one time passwords, which may be related. The current approach to prevent unregistered users is a long random password, so a new config boolean could be added and checked during connection. The comments suggest no maintainer response yet, so clarity is good but may need design input.