mumble-voip/mumble

Make Superuser remain accessible even through bans

Open

#3,898 opened on Nov 16, 2019

View on GitHub
 (16 comments) (1 reaction) (0 assignees)C++ (1,062 forks)batch import
Hacktoberfestfeature-requestgood first issuehelp wanted

Repository metrics

Stars
 (5,642 stars)
PR merge metrics
 (Avg merge 6d) (7 merged PRs in 30d)

Description

Why is Possible Ban Superuser?

2019-11-16 17:29:48.897 1 => Ignoring connection: 127.0.0.1:1581 (Global ban)

I think there is more Information needet,about Ban status to the User, and SuperUser Should ever Connnecting to the Server.

Contributor guide

Research direction
Examine the ban enforcement logic in the Mumble server, located in files like 'Server.cpp' or related to connection handling. Identify where global bans are checked and ensure that the SuperUser (UID 0 or specified superuser ID) is exempt from such checks. Consider adding a configuration option to control this behavior if not already present.
Tech stack
None
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Mumble server architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50