mumble-voip/mumble

configured sslciphers not respected.

Open

#6465 opened on Jun 12, 2024

View on GitHub
 (9 comments) (0 reactions) (0 assignees)C++ (5,642 stars) (1,062 forks)batch import
buggood first issueserver

Description

The issue

I configed sslCiphers=DHE-RSA-CHACHA20-POLY1305 in server ini to disable AES. However when starting server the following indicating it's not respected and clients still connecting with AES encryption.

2024-06-12 13:01:34.054 MetaParams: TLS cipher preference is "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:DHE-RSA-CHACHA20-POLY1305"

Mumble version

1.5.634

Mumble component

Server

OS

Linux

Additional information

No response

Contributor guide

Tech stack
cpp
Domain
backendsecurity
Issue type
bug
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-3 hours
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.
clear
Prerequisites
C++OpenSSLMumble server configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate how the sslCiphers configuration option is parsed and applied during server startup. Look at the MetaParams class and TLS cipher preference initialization in the Mumble server source code. Check if the configured ciphers are being overwritten by hardcoded defaults. Compare the configuration parsing logic in config files (e.g., ini parsing) to understand the discrepancy.