Mumble doesn't consider a TLS cert to match if the hostname is resolved via SRV

[ldesgoui]

Description

I have an SRV record for my hostname, I'm trying to serve a TLS cert for that hostname, Mumble is refusing to consider it valid.
I couldn't try with a cert for _mumble._tcp.<the hostname> as LetsEncrypt forbids it, since it wouldn't be a valid FQDN.

Steps to reproduce

1. Set up a SRV record (i.e. _mumble._tcp.example.com)
2. Acquire a TLS certificate for the hostname (i.e. example.com)
3. Run murmur
4. Connect to the server via the hostname (i.e. example.com)

Mumble version

1.5.0

Mumble component

Client

OS

Linux

Reproducible?

Yes

Additional information

No response

Relevant log output

Screenshots

[ldesgoui]

I just realized I should have tried adding the SRV target to the TLS cert, that's very logical in hindsight, and that fixed the problem