Obtaining a Let's Encrypt Murmur Certificate

From Mumble Wiki
Revision as of 11:36, 1 April 2017 by MKrautz (talk | contribs) (Do not use sslCA for fullchain, use sslCert instead.)
Jump to: navigation, search

Let's Encrypt provides a variety of ways how to get a certificate for your server for free but you must have a domain name you own, how to set up certbot or how to verify your domain depends on a high variety of factors, thus descibing the process for all the distributions is out of scope of this wiki entry. For Ubuntu 16.04 (with nginx) you can try this guide.

Using Let's Encrypt is an easy way to make sure the people connecting to your server know it's actually you that is hosting the server, as it's pretty hard to hijack Let's Encrypt to create a valid certificate for any malicious entity (unless your (DNS) server gets compromised).

Example configuration you may need to add or modify in your mumble-server.ini:

# These three .pem files should be the ones in the certificate folder letsencrypt created
# Murmur needs restarting to load new certificates
sslCert=[path to]/fullchain.pem
sslKey=[path to]/privkey.pem

# Has to be generated with for example sudo openssl dhparam -out /etc/ssl/certs/dhparam.pem 2048
sslDHParams=/etc/ssl/certs/dhparam.pem
# Just using HIGH does not work, the clients do not support the strongest ciphers
sslCiphers=EECDH+AESGCM:EDH+AESGCM:AES256-SHA:EDH+aRSA+AESGCM:AES256+EECDH:AES2