mumble-voip/mumble

configured sslciphers not respected.

Open

#6,465 创建于 2024年6月12日

在 GitHub 查看
 (9 评论) (0 反应) (0 负责人)C++ (5,642 star) (1,062 fork)batch import
buggood first issueserver

描述

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

贡献者指南

技术栈
cpp
领域
backendsecurity
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C++OpenSSLMumble server configuration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
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.