The Mumble team has released version 1.2.9 of the Mumble VoIP application. Version 1.2.9 is a maintenance release in the stable 1.2-series of Mumble.

This release contains a couple of bug fixes to the Mumble client and contains updates to various Mumble dependencies, most prominently OpenSSL (1.0.1n) and Qt 4.8 (latest from Git). It is also the first release in the 1.2.x series that enables TLS 1.2 and modern TLS cipher suites.

If you are using one our packaged static Murmur servers, or Murmur on Windows, or any of our packaged Mumble client packages we advise you to update to get the latest security fixes from our dependencies.

Changes in this release:

OpenSSL has been updated to 1.0.1n.

Qt 4.8 has been synced to the latest sources from Git.

Mumble and Murmur now use TLS 1.2 if the server/client combination allows it.

All of these changes are already available in our snapshot builds (the 1.3.x series), so if you like living on the bleeding edge and want to help out with Mumble development, feel free to check out our development snapshots at http://mumble.info/.

The TLS 1.2 support in our binary packages is backported from Qt 5. Unfortunately, that means that if you are using Mumble from a package manager, you’re not going to get a TLS 1.2-enabled build.

We do not advise distributions to pick up these patches as-is. In particular, they change the meaning of QSsl::TlsV1 to mean ‘TLS 1.0 or later’. This is not desirable to the vast majority of software out there — but it works for Mumble’s binary packages. If there are any distributions out there willing to carry this diff to their Qt 4 packages to allow TLS 1.2 support for Mumble 1.2.9, we’re willing to prepare a more fitting patch to Qt 4.8 that implements the behavior of “QSsl::TlsV1_0OrLater” from the upcoming Qt 5.5 release.

As you might have already noticed we changed the hosting for our wiki as well as the forums. Especially if our previous forums hosted at SourceForge gave you trouble or the slow loading when editing the wiki made you sad this is the time to take another look.

We have finally finished integrating Transifex into our workflow. Transifex is an online translation tool which allows collaborative translation of applications directly from a browser.

For Mumble this means that it is now easier than ever before to contribute translations for your language to the project. Simply visit our Transifex project page, sign up and get started. For a step by step guide see this page in our wiki.

The Mumble team has released version 1.2.8 of the Mumble VoIP application. This is a minor bug fix release in the stable 1.2-series of Mumble.

This release contains a couple of bug fixes to the Mumble client and updates OpenSSL to version 1.0.0n due to an OpenSSL security advisory. We advise our users to download this update as soon as possible from our SourceForge downloads page: http://sourceforge.net/projects/mumble/files/Mumble/1.2.8/

The Mumble team has released version 1.2.7 of the Mumble VoIP application. This is a minor bug fix release in the stable 1.2-series of Mumble.

This release contains a couple of bug fixes to the Mumble client and updates OpenSSL to version 1.0.0m due to an OpenSSL security advisory. We advise our users to download this update as soon as possible from our SourceForge downloads page: http://sourceforge.net/projects/mumble/files/Mumble/1.2.7/

Most of the Mumble project’s communication this week regarding the Heartbleed vulnerability has happened via IRC. This blog post attempts to fix that by providing answers to the most frequently asked questions here on our blog.

A word of warning: ‘Mumble for iOS’ 1.2.3 is incredibly unusable on iOS 7.1 – if you depend on it, you should probably not update to iOS 7.1 just yet.﻿

There is a problem with audio subsystem, which is causing it to endlessly try to restart itself. This manifests itself via iOS’s ‘red bar’ (signalling that an app is using background audio) toggling itself on and off very fast (even when inside the app!), making the app unusable.

We’ve identified the problem, and we’re working on a fix. If you’ve already updated to iOS 7.1, fear not! We’ve also found a workaround which, while inconvenient, should help you work around the issue until a proper fix has been released.