mumble-server crashes at launch without libssl1.0-dev

[Zachary Clifford]

This bug is with mumble-server (1.2.19-1ubuntu1) on Bionic.

I installed mumble-server in a stripped down Docker container, but the murmur server fails to start because it's linked against libssl 1.0. Bionic now has 1.1 available at runtime. The error message printed is:

Invalid sslCiphers option. Either the cipher string is invalid or none of the ciphers are available: "EECDH+AESGCM:AES256-SHA:AES128-SHA"

Which lines up with this thread:

https://stackoverflow.com/questions/42094214/why-is-qsslsocket-working-with-qt-5-3-but-not-qt-5-7-on-debian-stretch

Looking at the changelog, I suspect this came about in mumble 1.2.19-1build1 where mumble was rebuilt with openssl1.1, but the murmur server still expects an older one.

I was able to work around by installing libssl1.0-dev in addition to mumble-server. Maybe the server can be rebuilt, or libssl1.0-dev can be added as a dependency of mumble-server?

For reference, my (working) Dockerfile is:

FROM ubuntu:latest

RUN apt-get update && apt-get install -y mumble-server libssl1.0-dev && \
    rm -rf /var/lib/apt/lists/*

COPY ./mumble-server.ini /etc/mumble-server.ini

EXPOSE 64738/tcp 64738/udp

# The following directory must be mapped out of the container.
# VOLUME murmurdata:/var/lib/mumble-server

ENTRYPOINT ["/usr/sbin/murmurd", "-fg", "-v"]
CMD ["-ini", "/etc/mumble-server.ini"]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Captain Skyhawk (captain-skyhawk)]

Confirmed when working with Docker/Mumble.