mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Registration: handle certificates without Client Auth in EKU #130
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#130
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mkrautz on GitHub (Dec 15, 2013).
When a server registers with the Mumble public server list's master server, the server uses its certificate as a client certificate.
Some certificates, such as StartCom's Class 1 Server Certificates (the free ones), do not have Client Authentication set in their Extended Key usage.
This causes the registration TLS handshake to fail. The registration server is a Perl script sitting behind mod_perl, so the entity responsible for the handshake is Apache.
Modifying Apache to fit our use-case seems to be a big maintenance burden.
Perhaps we should detect whether the Client Auth EKU is present in the server's certificate, and if that's the case, we could generate an ephemeral "container" X.509 certificate, containing the server's real certificate chain in extension (or similar mechansim).
This certficiate would be generated each time a registration happens.
Suggestions welcomed.