http://sourceforge.net/projects/mumble/files/Mumble/1.2.3a/mumble-1.2.3a.msi/download (uninstall 1.2.3 stable first).
An updated installer for the snapshot version is available from: https://mumble.info/snapshot/mumble-1.2.3-271-gca8b25c.msi
You can also download a fixed Mumble.exe for the 1.2.3 stable from: http://sourceforge.net/projects/mumble/files/Mumble/1.2.3a/mumble-1.2.3-resigned-binary.zip/download
+http://sourceforge.net/projects/mumble/files/Mumble/1.2.3a/mumble-1.2.3a.msi/download (uninstall +1.2.3 stable first).
An updated installer for the snapshot version is available from: +https://mumble.info/snapshot/mumble-1.2.3-271-gca8b25c.msi
+You can also download a fixed Mumble.exe for the 1.2.3 stable from: +http://sourceforge.net/projects/mumble/files/Mumble/1.2.3a/mumble-1.2.3-resigned-binary.zip/download
-
-Mumble, like most sound systems, uses a **left handed coordinate system** ([see this for a visual representation](https://docs.microsoft.com/en-us/windows/win32/direct3d9/coordinate-systems)).
-
-As a visualization of the left handed coordinate system: If you imagine yourself looking over a large empty field; X increases towards your right, Y increases above your head, and Z increases in front of you. In other words, if we place origin in your chest and you stretch your arms out to your sides, your right hand will be `(1,0,0)`, your left hand will be `(-1,0,0)` and your head will be `(0,0.2,0)`. If you then stretch your arms out in front of you instead, they'll become `(0,0,1)`.
-
-We need three vectors. First is the position vector. This should be in meters, so you may need to scale it. The reason: If it is not in meters, distance attenuation will be different to the other games/plugins, meaning users will have a bad experience with positional audio (audio configuration is dependant on a common distance measurement).
-
-The next two vectors are the heading. These should be unit vectors (length one), and should be perpendicular (to one another). The first vector is the front vector, which is simply the direction you are looking in. The second is the top vector, which is an imaginary vector pointing straight out the top of your head. If you do not supply a top vector, Mumble will assume you have a “Y-is-up” coordinate system and that the user can not tilt their head, and then compute the top vector based on that.
-
-## Method 1: Memory Searching
-
-Warning: Be aware that the tools/methods used in this tutorial might trigger anti cheat protection. Read the sections below carefully before attempting to use them on a game.
-Note that Mumble does NOT support cheating of any kind.
-
-This works well for most games which think of the player as a static object, meaning the data's location in memory is fixed. This is the fastest method, so it's recommended you start with this.
-
-### Initial setup
-
-First, start the game, read the documentation, websites, whatever you can find, and see if there is a way to have the game display your current position. If there is then you'll have a much easier time validating your data.
-
-Then start the game. Try to find a piece of geometry that's aligned along an axis; if there's a compass or minimap, point due north.
-
-### Finding the position offset
-
-Start your preferred cheating utility.
-
-If you don't have it, choose one from the list under [Memory Analysis Tools]({{< relref "memory-analysis-tools" >}}).
-
-#### If you have the in-game position
-
-Search for a floating point value around the X value. (IE, if the game reports your position as 357.3, search for a value between 357.2 and 357.4). Move a bit, repeat. When you've narrowed it down to just one possible address (or set of addresses), write them down.
-
-Repeat for Y and Z.
-
-#### If you don't have the in-game position
-
-Make a memory snapshot. Move forward. Search for a floating point value that increased. Move backward. Search for a floating point value that decreased. Repeat. If you don't find any values at all, the game might have reversed the axis; so turn 180 degrees and try again.
-
-When you find the X value, turn 90 degrees right and search for the Y value, and then the Z value.
-
-#### When you have the positions
-
-Based on the addresses you have, we're looking for just one triplet of (XYZ) addresses. They should be right next to each other in memory, ideally 4 or 8 bytes apart. Note down all positions that match.
-
-Now, and this is important; quit the game, restart your machine and start the game again, but this time do so with a different map, a different character, different graphics settings, different audio; in short, change everything you can but the actual game.
-
-Start your cheat utility again and go through all the addresses you have. If they still match, you can use this method. If they don't, the game dynamically allocates the position in memory, and you'll have to use another method.
-
-## Finding the heading
-
-Once you have the position, you can find the heading with the same method. Since you now know what is the positive direction of the X axis, position yourself so you are looking straight down it. Your 'front' heading should be (1,0,0), so search for a floating point value between 0.7 and 1.05. Turn 180 degrees and search for a value between -0.7 and -1.05. Repeat for Y and Z.
-
-The top vector is done the exact same way, just look down into the ground when finding X; your head now points along the X axis. Note that some games do not have a top vector; a top vector is only "needed" if the game allows you to tilt your head from side to side.
-
-## Peeking at the code
-
-This is the second method, to be used if the first doesn't work. Note that this method requires advanced disassembly knowledge, so if you're capable of doing this, you probably don't need a guide. So, this will be brief.
-
-### Quality disassembly
-
-You need a quality disassembler or debugger. A good one is IDA Pro, but it's a tad expensive.
-
-### Finding the game's positional audio
-
-The trick we're going to use is this; most games already have positional audio support, so we're looking for their audio code. Their audio code needs the position and heading, so we simply rip that particular piece of data :)
-
-Note that most games will rotate and move the game world; they will set the listener to always be at origo, looking straight down the Z axis, and then they will rotate and translate all the sound-sources before passing parameters to the sound system (OpenAL/DirectSound/FMOD). We found this out the hard way; we had a really cool plugin which injected into OpenAL and DirectSound and took the position of the speaker from there, but in 90% of the games that gave us origo instead.
-
-First you need to figure out which sound technology the game uses, and then proceed from there.
-
-#### FMOD
-
-If it’s using FMOD, it will say so in the documentation and most likely on the loading screen. FMOD can be statically linked to the application. If it is, you’re going to have a much harder time of things. If it’s a DLL, you can find the import table and backtrack the calls to find the game's audio routines.
-
-#### OpenAL
-
-OpenAL will always be loaded dynamically, so just start the game, break it in a debugger and look for the openal, openal32 etc libraries. If it’s there, the game is using OpenAL.
-
-#### DirectSound
-
-If the game is using *directsound*, it will load the `dsound.dll`, and will at some point call `DirectSoundCreate8()`. Search for the call, find out where the game stores the object pointer and look for other routines which access it.
-
-### Using a debugger to speed things up
-
-You can speed things up considerably by using a debugger and some creative breakpointing. Set a breakpoint on all the functions in the Audio API which set the position of either the listener or the source. The game will break, and the stack backtrace will give you the module offsets for the audio code.
-
-### What to do when you have the code?
-
-With a bit of luck, the code for setting the source position includes some fancy matrix multiplication; the matrix being multiplied with is based on your current position and heading, so find the code which computes it and you'll have your ingame position and heading.
+---
+title: "Creating a Plugin"
+---
+
+This is an abstract overview of how to add positional audio support; for step-by-step instructions, see the Pluginguide.
+
+## What is needed for positional audio
+
+For positional audio, we need two things: Your position in the 3D world, and the direction you are looking in. If you
+have access to the source code for the game, exporting this to Mumble is easy, just use the Link plugin. If this is a
+3rd party game, we'll have to extract the position from the running game.
+
+If you have any questions regarding the process hit us up in
+[`#mumble-dev:matrix.org`](https://matrix.to/#/#mumble-dev:matrix.org) and we will try to help.
+
+We also accept new plugins into our codebase as long as you are willing to support them. Be aware however that we might
+reject plugins for games with short update cycles as our current distribution method makes keeping those working for
+longer times quite painful. When in doubt please verify with us before puttin in the work.
+
+## Data
+
+
+
+Mumble, like most sound systems, uses a **left handed coordinate system**
+([see this for a visual representation](https://docs.microsoft.com/en-us/windows/win32/direct3d9/coordinate-systems)).
+
+As a visualization of the left handed coordinate system: If you imagine yourself looking over a large empty field; X
+increases towards your right, Y increases above your head, and Z increases in front of you. In other words, if we place
+origin in your chest and you stretch your arms out to your sides, your right hand will be `(1,0,0)`, your left hand will
+be `(-1,0,0)` and your head will be `(0,0.2,0)`. If you then stretch your arms out in front of you instead, they'll
+become `(0,0,1)`.
+
+We need three vectors. First is the position vector. This should be in meters, so you may need to scale it. The reason:
+If it is not in meters, distance attenuation will be different to the other games/plugins, meaning users will have a bad
+experience with positional audio (audio configuration is dependant on a common distance measurement).
+
+The next two vectors are the heading. These should be unit vectors (length one), and should be perpendicular (to one
+another). The first vector is the front vector, which is simply the direction you are looking in. The second is the top
+vector, which is an imaginary vector pointing straight out the top of your head. If you do not supply a top vector,
+Mumble will assume you have a “Y-is-up” coordinate system and that the user can not tilt their head, and then compute
+the top vector based on that.
+
+## Method 1: Memory Searching
+
+Warning: Be aware that the tools/methods used in this tutorial might trigger anti cheat protection. Read the sections
+below carefully before attempting to use them on a game.
+Note that Mumble does NOT support cheating of any kind.
+
+This works well for most games which think of the player as a static object, meaning the data's location in memory is
+fixed. This is the fastest method, so it's recommended you start with this.
+
+### Initial setup
+
+First, start the game, read the documentation, websites, whatever you can find, and see if there is a way to have the
+game display your current position. If there is then you'll have a much easier time validating your data.
+
+Then start the game. Try to find a piece of geometry that's aligned along an axis; if there's a compass or minimap,
+point due north.
+
+### Finding the position offset
+
+Start your preferred cheating utility.
+
+If you don't have it, choose one from the list under [Memory Analysis Tools]({{< relref "memory-analysis-tools" >}}).
+
+#### If you have the in-game position
+
+Search for a floating point value around the X value. (IE, if the game reports your position as 357.3, search for a
+value between 357.2 and 357.4). Move a bit, repeat. When you've narrowed it down to just one possible address (or set of
+addresses), write them down.
+
+Repeat for Y and Z.
+
+#### If you don't have the in-game position
+
+Make a memory snapshot. Move forward. Search for a floating point value that increased. Move backward. Search for a
+floating point value that decreased. Repeat. If you don't find any values at all, the game might have reversed the axis;
+so turn 180 degrees and try again.
+
+When you find the X value, turn 90 degrees right and search for the Y value, and then the Z value.
+
+#### When you have the positions
+
+Based on the addresses you have, we're looking for just one triplet of (XYZ) addresses. They should be right next to
+each other in memory, ideally 4 or 8 bytes apart. Note down all positions that match.
+
+Now, and this is important; quit the game, restart your machine and start the game again, but this time do so with a
+different map, a different character, different graphics settings, different audio; in short, change everything you can
+but the actual game.
+
+Start your cheat utility again and go through all the addresses you have. If they still match, you can use this method.
+If they don't, the game dynamically allocates the position in memory, and you'll have to use another method.
+
+## Finding the heading
+
+Once you have the position, you can find the heading with the same method. Since you now know what is the positive
+direction of the X axis, position yourself so you are looking straight down it. Your 'front' heading should be (1,0,0),
+so search for a floating point value between 0.7 and 1.05. Turn 180 degrees and search for a value between -0.7 and
+-1.05. Repeat for Y and Z.
+
+The top vector is done the exact same way, just look down into the ground when finding X; your head now points along the
+X axis. Note that some games do not have a top vector; a top vector is only "needed" if the game allows you to tilt your
+head from side to side.
+
+## Peeking at the code
+
+This is the second method, to be used if the first doesn't work. Note that this method requires advanced disassembly
+knowledge, so if you're capable of doing this, you probably don't need a guide. So, this will be brief.
+
+### Quality disassembly
+
+You need a quality disassembler or debugger. A good one is IDA Pro, but it's a tad expensive.
+
+### Finding the game's positional audio
+
+The trick we're going to use is this; most games already have positional audio support, so we're looking for their audio
+code. Their audio code needs the position and heading, so we simply rip that particular piece of data :)
+
+Note that most games will rotate and move the game world; they will set the listener to always be at origo, looking
+straight down the Z axis, and then they will rotate and translate all the sound-sources before passing parameters to the
+sound system (OpenAL/DirectSound/FMOD). We found this out the hard way; we had a really cool plugin which injected into
+OpenAL and DirectSound and took the position of the speaker from there, but in 90% of the games that gave us origo
+instead.
+
+First you need to figure out which sound technology the game uses, and then proceed from there.
+
+#### FMOD
+
+If it’s using FMOD, it will say so in the documentation and most likely on the loading screen. FMOD can be statically
+linked to the application. If it is, you’re going to have a much harder time of things. If it’s a DLL, you can find the
+import table and backtrack the calls to find the game's audio routines.
+
+#### OpenAL
+
+OpenAL will always be loaded dynamically, so just start the game, break it in a debugger and look for the openal,
+openal32 etc libraries. If it’s there, the game is using OpenAL.
+
+#### DirectSound
+
+If the game is using _directsound_, it will load the `dsound.dll`, and will at some point call `DirectSoundCreate8()`.
+Search for the call, find out where the game stores the object pointer and look for other routines which access it.
+
+### Using a debugger to speed things up
+
+You can speed things up considerably by using a debugger and some creative breakpointing. Set a breakpoint on all the
+functions in the Audio API which set the position of either the listener or the source. The game will break, and the
+stack backtrace will give you the module offsets for the audio code.
+
+### What to do when you have the code?
+
+With a bit of luck, the code for setting the source position includes some fancy matrix multiplication; the matrix being
+multiplied with is based on your current position and heading, so find the code which computes it and you'll have your
+ingame position and heading.
diff --git a/hugo/content/documentation/developer/positional-audio/create-plugin/guide/index.md b/hugo/content/documentation/developer/positional-audio/create-plugin/guide/index.md
index abef18e9..de3ac2c4 100644
--- a/hugo/content/documentation/developer/positional-audio/create-plugin/guide/index.md
+++ b/hugo/content/documentation/developer/positional-audio/create-plugin/guide/index.md
@@ -1,584 +1,709 @@
----
-title: "Guide to Creating a Plugin"
----
-Warning: Be aware that the tools/methods used in this tutorial might trigger anti cheat protection. Read the sections below (e.g. this) carefully before attempting to use them on a game.
-
-Game positional audio is a feature of Mumble that many users consider very useful. However, creating the game plugin can sometimes be complicated, and for the average person, daunting. This guide will help you understand how a game plugin works, what it does, and how you can make one.
-
-If you have any questions regarding the process hit us up in [`#mumble-dev:matrix.org`](https://matrix.to/#/#mumble-dev:matrix.org) and we will try to help.
-
-We also accept new plugins into our codebase as long as you are willing to support them. Be aware however that we might reject plugins for games with short update cycles as our current distribution method makes keeping those working for longer times quite painful. When in doubt please verify with us before puttin in the work.
-
-This guide is supposed to be a step-by-step tutorial for the general case. For a more abstract view and more methodology take a look at [the introduction]({{< relref ".." >}}).
-
-## Prerequisites
-
-### Programs needed
-
-[Analysis Tools]({{< relref "memory-analysis-tools" >}})
-
-#### Tools
-
-C++ IDE and compiler. Read the entire section to know what IDE/Compiler is right for you.
-
-[MumblePAHelper](http://upload.dbclan.de/MumblePAHelper_VS2010.exe). **This binary is built with MSVC 2010, it doesn't work with plugins built with other compilers or MSVC versions.**
-This is a useful tool to quickly see if your plugin is working as it should. Simply place it together with `QtCore4.dll` and `QtGui4.dll` (found in the Mumble directory) in your `%APPDATA%\Mumble` folder and run it while your game is running, and it will show if the plugin is linked, if the positional coordinates are working properly, etc. Note that it will only show the plugins which are present inside %APPDATA%\Mumble\plugins.
-
-[Notepad++](https://notepad-plus-plus.org/) (optional). After you install Notepad++, start it, go to Preferences -> New Document/Default Directory, and check "Unix" in the Format box.
-
-### Learn a Little C++
-
-Although you do not need to be an expert programmer in order to write a plugin, you do need to understand fundamental data types. Here are a few of the most important:
-
-float: This is the data type that almost all positional audio game addresses use. They are 32 bit, decimal numbers stored in the memory. A float data type is 4 bytes * 8 = 32 bits. An example of a floating point value would be "1234.0123456".
-
-byte: This is the smallest data type in Intel x86-based computing. This type of memory address holds 1 byte of information (1 byte * 8 = 8 bits). From this type of memory address, you can get 0-255 base^10 values, or -127 to 128, depending on whether or not you use a signed byte (it has a + or - on the front of the value), or an unsigned byte (no + or -). An example of a byte value would be "12".
-
-In C++, you must declare a variable before you can use it. If you want to use a float variable, you declare it with
-
-```cpp
-float 
-
-Mumble can show information within rendered applications; most notably videogames which are typically used with full screen rendering.
-
-Mumble can show connected and/or talking voice participants as well as current FPS and/or the clock time.
-
-The overlay can give users feedback about who is connected or who is talking when the application would otherwise obscure this information. Even if the user has Mumble open on a second monitor, the overlay may be a useful addition as it can be placed freely on the primarily focused on monitor.
-
-Mumble hooks into 3D rendering technology. On **Windows** it currently **supports Direct3D 9/10/11 and OpenGL**. On **Linux and macOS** it supports **OpenGL**. Both 32- and 64-bit applications are supported.
-
-## Support Tables
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-### Incompatible Games
-
-The following games are known to have issues with the Mumble overlay:
-
-| API | Support |
|---|---|
| Vulkan | since 1.3.0 |
| OpenGL | since 1.3.0 |
| Direct3D 12 | does not display |
| Direct3D 11 | since 1.3.0 |
| Direct3D 10 | since 1.3.0 |
| Direct3D 9ex | since 1.3.0 |
| Direct3D 9 | since 1.3.0 |
| API | Support |
|---|---|
| Vulkan | since 1.3.0 |
| OpenGL | supported |
| Direct3D 12 | does not display |
| Direct3D 11 | supported |
| Direct3D 10 | supported |
| Direct3D 9ex | supported |
| Direct3D 9 | supported |
| API | Support |
|---|---|
| Vulkan | since 1.3.0 |
| OpenGL | supported |
| Game | Last Updated | API | Comments | Fixed in |
|---|---|---|---|---|
| Combat Arms | unknown | overlay causes CA to crash after map changes; overlay will not display unless one joins a server and then leaves it | unknown | |
| Vanguard | unknown | crashes to desktop when overlay is enabled | unknown | |
| Call of Duty 4 | unknown | PunkBuster kick playing online | unknown | |
| Call of Duty 2 | unknown | PunkBuster kick playing online | unknown | |
| Killing Floor | unknown | the game will crash when changing resolutions or going into fullscreen mode | unknown | |
| Red Orchestra | unknown | the game will crash when changing resolutions or going into fullscreen mode | unknown | |
| H1Z1 | unknown | game crashes at startup | unknown |
+
+Mumble can show information within rendered applications; most notably videogames which are typically used with full
+screen rendering.
+
+Mumble can show connected and/or talking voice participants as well as current FPS and/or the clock time.
+
+The overlay can give users feedback about who is connected or who is talking when the application would otherwise
+obscure this information. Even if the user has Mumble open on a second monitor, the overlay may be a useful addition as
+it can be placed freely on the primarily focused on monitor.
+
+Mumble hooks into 3D rendering technology. On **Windows** it currently **supports Direct3D 9/10/11 and OpenGL**. On
+**Linux and macOS** it supports **OpenGL**. Both 32- and 64-bit applications are supported.
+
+## Support Tables
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Incompatible Games
+
+The following games are known to have issues with the Mumble overlay:
+
+| API | Support |
|---|---|
| Vulkan | since 1.3.0 |
| OpenGL | since 1.3.0 |
| Direct3D 12 | does not display |
| Direct3D 11 | since 1.3.0 |
| Direct3D 10 | since 1.3.0 |
| Direct3D 9ex | since 1.3.0 |
| Direct3D 9 | since 1.3.0 |
| API | Support |
|---|---|
| Vulkan | since 1.3.0 |
| OpenGL | supported |
| Direct3D 12 | does not display |
| Direct3D 11 | supported |
| Direct3D 10 | supported |
| Direct3D 9ex | supported |
| Direct3D 9 | supported |
| API | Support |
|---|---|
| Vulkan | since 1.3.0 |
| OpenGL | supported |
| Game | Last Updated | API | Comments | Fixed in |
|---|---|---|---|---|
| Combat Arms | unknown | overlay causes CA to crash after map changes; overlay will not display unless one joins a server and then leaves it | unknown | |
| Vanguard | unknown | crashes to desktop when overlay is enabled | unknown | |
| Call of Duty 4 | unknown | PunkBuster kick playing online | unknown | |
| Call of Duty 2 | unknown | PunkBuster kick playing online | unknown | |
| Killing Floor | unknown | the game will crash when changing resolutions or going into fullscreen mode | unknown | |
| Red Orchestra | unknown | the game will crash when changing resolutions or going into fullscreen mode | unknown | |
| H1Z1 | unknown | game crashes at startup | unknown |
-
-6\. You should see that a "mumble" profile has been created
-
-
-
-
-
-7\. Right click the mumble profile and select **"Set as Default"** or **"Set as Persistent"**.
-
-This is required due to limitations of the Logitech G-key API, since it was designed for use only with games in mind.
-
-*We recommend setting the mumble profile as default.*
-
-*For more information, see "What are persistent and default profiles?" in the LGS help by clicking on the "?" icon on the LGS window, or in [the online manual (PDF)(page 54)](http://www.logitech.com/assets/51813/3/lgs-guide.pdf).*
-
-*If mumble is not set as the default or persistent profile, then your keys will not be active unless mumble is the active window.*
-
-
-
-
-
-8\. In Mumble, you should now be able to set G-keys as your shortcut keys
-
-
++++
+title = "Logitech G-Keys"
++++
+
+The G-keys available on many Logitech keyboards can be used as keyboard shortcuts in Mumble 1.3.0 and later.
+
+## First-time setup
+
+Install the [Logitech Gaming Software (LGS)](http://support.logitech.com/en_ca/software/gaming-software).
+
+If it is already installed, ensure it is at least version 8.55.
+
+1\. Launch LGS
+
+2\. Launch or restart Mumble.
+
+3\. Open the LGS window
+
+
+
+5\. Open the G-keys view
+
+
+
+6\. You should see that a "mumble" profile has been created
+
+
+
+
+
+7\. Right click the mumble profile and select **"Set as Default"** or **"Set as Persistent"**.
+
+This is required due to limitations of the Logitech G-key API, since it was designed for use only with games in mind.
+
+_We recommend setting the mumble profile as default._
+
+_For more information, see "What are persistent and default profiles?" in the LGS help by clicking on the "?" icon on
+the LGS window, or in [the online manual (PDF)(page 54)](http://www.logitech.com/assets/51813/3/lgs-guide.pdf)._
+
+_If mumble is not set as the default or persistent profile, then your keys will not be active unless mumble is the
+active window._
+
+
+
+
+
+8\. In Mumble, you should now be able to set G-keys as your shortcut keys
+
+
diff --git a/hugo/content/documentation/user/macos/overlay-on-macos/index.md b/hugo/content/documentation/user/macos/overlay-on-macos/index.md
index 4a5730e7..9fb17b1e 100644
--- a/hugo/content/documentation/user/macos/overlay-on-macos/index.md
+++ b/hugo/content/documentation/user/macos/overlay-on-macos/index.md
@@ -1,12 +1,14 @@
----
-title: "Mumble Overlay on macOS"
----
-The Mumble in-game Overlay allows you to see who is talking, the game's FPS, and the current time within videogames.
-
-Mumble installs on macOS without administrative rights. But the Overlay requires administrative rights to be able to show up within games. Consequently, an additional setup step is necessary.
-
-To install the Mumble Overlay:
-
-1. Launch Mumble
-2. Open the Settings window and open the Overlay section
-3. Install the overlay from here
+---
+title: "Mumble Overlay on macOS"
+---
+
+The Mumble in-game Overlay allows you to see who is talking, the game's FPS, and the current time within videogames.
+
+Mumble installs on macOS without administrative rights. But the Overlay requires administrative rights to be able to
+show up within games. Consequently, an additional setup step is necessary.
+
+To install the Mumble Overlay:
+
+1. Launch Mumble
+2. Open the Settings window and open the Overlay section
+3. Install the overlay from here
diff --git a/hugo/content/documentation/user/mumble-url/index.md b/hugo/content/documentation/user/mumble-url/index.md
index 32f60e30..60a59b80 100644
--- a/hugo/content/documentation/user/mumble-url/index.md
+++ b/hugo/content/documentation/user/mumble-url/index.md
@@ -1,95 +1,105 @@
----
-title: "Mumble URL"
----
-Mumble defines it's own `mumble://` URL scheme to share links to servers and channels and to be able to connect to them directly.
-
-On Windows the installer will register `mumble://` links to be opened with Mumble.
-
-Mumble links can be opened on the command line by passing them to mumble.exe too:
-
-```
-mumble.exe mumble://example.com/
-```
-
-or with a channel path:
-
-```
-mumble.exe mumble://example.com/ChanA/ChanB
-```
-
-You can get get a URL in the Channel context menu (right click):
-
-
-
-## Connect Behavior
-
-When opening a Mumble link the Mumble client will connect to the server.
-
-* If you are already registered you will connect with your account
-* If the URL contains a username that username will be used
-* If no username is determined, the client will ask with what name you want to connect with
-
-## URL Format
-
-```
-mumble://[username[:password]@][:port]/[channelpath][?title=
-
-If someone is NOT using Positional Audio, you hear them normal, not from a specific direction or location.
-
-If someone uses Positional Audio, and is in the same context (game session) you will hear them from the direction they are in and with varying volume depending on how close they are.
-
-The variance of the system, like maximum distance you hear people, or minimum volume, can be configured in the Mumble PA settings.
-
-## How Mumble gets information about the virtual positions of the participants
-
-Mumble can get the position information and context in two ways:
-
-1. The Game itself shares context and position information
-2. A Mumble plugin is created and installed that reads the game’s memory for context and position information
-
-Because the second process reads from a games memory, any game update may require updates to the plugin too. How robust the plugin is against new versions and memory layout changes depends on the plugin implementation.
-
-If a plugin becomes outdated (it no longer works) please [check for an existing ticket for it, and create one in our issue tracker](https://github.com/mumble-voip/mumble/issues) if it does not exist yet. Providing version information or offering help updating will help implementing support for the updated version.
-
-### PA Data
-
-* Position and orientation of your avatar in-game
-* Position and orientation of the in-game camera
-* A so called “context” uniquely identifying the game session and possibly team *(as in server or realm, or server + team)*
-* A so called “identity” uniquely identifying the client amongst other clients within the same "context", possibly with additional information like class or team
-
-The server will only transmit positional audio data to clients with a matching context. Users with a different context will be heard normally. The context and identity information are not forwarded to the other clients, but can be used by server side applications which can, for example, place players in different channels/groups depending on the server or team they are currently playing on/in.
-
-## Positional Audio Settings
-
-### Plugin Configuration
-
-A plugin may have configuration options. If it does the Configure button will open a dialog for the selected plugin.
-
-Currently the only Plugin that has such a page is the “Manual Positional Audio” Plugin.
-
-See [Manual Plugin]({{< relref "/documentation/user/positional-audio/manual-plugin" >}})
-
-## Supported Engines, Games and Game Mods
-
-See the [list of supported engines, games and game mods]({{< relref "supported-games" >}})
+---
+title: "Mumble Positional Audio Documentation"
+---
+
+**Please note that Mumble works with all games as a regular voice chat application.**
+
+This page documents the positional audio (“PA”) feature specifically, where you hear participating users according to
+their position in your game world.
+
+## What is Positional Audio
+
+Positional Audio is a feature of Mumble that places the people talking to you in a certain position relative to your own
+depending on their actual position in the game you are playing. This way you can hear the person as if their actual
+avatar in-game was talking to you.
+
+
+
+If someone is NOT using Positional Audio, you hear them normal, not from a specific direction or location.
+
+If someone uses Positional Audio, and is in the same context (game session) you will hear them from the direction they
+are in and with varying volume depending on how close they are.
+
+The variance of the system, like maximum distance you hear people, or minimum volume, can be configured in the Mumble PA
+settings.
+
+## How Mumble gets information about the virtual positions of the participants
+
+Mumble can get the position information and context in two ways:
+
+1. The Game itself shares context and position information
+2. A Mumble plugin is created and installed that reads the game’s memory for context and position information
+
+Because the second process reads from a games memory, any game update may require updates to the plugin too. How robust
+the plugin is against new versions and memory layout changes depends on the plugin implementation.
+
+If a plugin becomes outdated (it no longer works) please
+[check for an existing ticket for it, and create one in our issue tracker](https://github.com/mumble-voip/mumble/issues)
+if it does not exist yet. Providing version information or offering help updating will help implementing support for the
+updated version.
+
+### PA Data
+
+- Position and orientation of your avatar in-game
+- Position and orientation of the in-game camera
+- A so called “context” uniquely identifying the game session and possibly team _(as in server or realm, or server +
+ team)_
+- A so called “identity” uniquely identifying the client amongst other clients within the same "context", possibly with
+ additional information like class or team
+
+The server will only transmit positional audio data to clients with a matching context. Users with a different context
+will be heard normally. The context and identity information are not forwarded to the other clients, but can be used by
+server side applications which can, for example, place players in different channels/groups depending on the server or
+team they are currently playing on/in.
+
+## Positional Audio Settings
+
+### Plugin Configuration
+
+A plugin may have configuration options. If it does the Configure button will open a dialog for the selected plugin.
+
+Currently the only Plugin that has such a page is the “Manual Positional Audio” Plugin.
+
+See [Manual Plugin]({{< relref "/documentation/user/positional-audio/manual-plugin" >}})
+
+## Supported Engines, Games and Game Mods
+
+See the [list of supported engines, games and game mods]({{< relref "supported-games" >}})
diff --git a/hugo/content/documentation/user/positional-audio/manual-plugin/index.md b/hugo/content/documentation/user/positional-audio/manual-plugin/index.md
index ea8deb99..0700a71d 100644
--- a/hugo/content/documentation/user/positional-audio/manual-plugin/index.md
+++ b/hugo/content/documentation/user/positional-audio/manual-plugin/index.md
@@ -1,17 +1,22 @@
----
-title: "Manual Positional Audio Plugin"
----
-In addition to the mentioned plugins, there is a special plugin called manual placement plugin. It does not require a game. Instead you can configure the plugin itself to set your own position from which other people in the same channel who set up the same context can hear you.
-
-
-
-1. Set yourself on the canvas from where others should hear you. Make sure to choose a position other than 0, 0, 0 or you won't hear or send positionally.
-2. Set your own orientation where you want your virtual avatar to look at on a 360° Scale.
-3. Set your own azimuth (if you look up or down while you talk).
-4. Set the context of your avatar. Only the people with the same context will hear you positionally.
-5. Set the identity.
-6. Link or unlink the plugin to transfer the settings to the server for processing.
-7. Enable or disable the plugin.
-8. Separate the plugin settings window. This is useful to change the positional audio settings without keeping the Mumble settings window opened.
-9. Reset values for all settings.
-10. Close the window.
+---
+title: "Manual Positional Audio Plugin"
+---
+
+In addition to the mentioned plugins, there is a special plugin called manual placement plugin. It does not require a
+game. Instead you can configure the plugin itself to set your own position from which other people in the same channel
+who set up the same context can hear you.
+
+
+
+1. Set yourself on the canvas from where others should hear you. Make sure to choose a position other than 0, 0, 0 or
+ you won't hear or send positionally.
+2. Set your own orientation where you want your virtual avatar to look at on a 360° Scale.
+3. Set your own azimuth (if you look up or down while you talk).
+4. Set the context of your avatar. Only the people with the same context will hear you positionally.
+5. Set the identity.
+6. Link or unlink the plugin to transfer the settings to the server for processing.
+7. Enable or disable the plugin.
+8. Separate the plugin settings window. This is useful to change the positional audio settings without keeping the
+ Mumble settings window opened.
+9. Reset values for all settings.
+10. Close the window.
diff --git a/hugo/content/documentation/user/positional-audio/supported-games.md b/hugo/content/documentation/user/positional-audio/supported-games.md
index 777c1cc9..6766c0e6 100644
--- a/hugo/content/documentation/user/positional-audio/supported-games.md
+++ b/hugo/content/documentation/user/positional-audio/supported-games.md
@@ -1,119 +1,122 @@
----
-title: "Games, Engines, and Game Mods supporting Mumble Positional Audio"
----
-**NOTE:** Plugins for 64-bit games only work with Mumble x64!
-
-*Note for Linux users:* Windows plugins work on Wine!
-
-The following tables display which games positional audio is available for, from which game version on (/for which version), for what platform and if extended support is available.
-
-Mumble version 1.2 introduced additional, extended positional audio features. Tooltips on this column’s content may indicate more information on what data is provided.
-
-## Native Support
-
-Games and game engines that provide native support remain functional across game updates.
-
-*Developer reference: [See developer integration documentation]({{< relref "/documentation/developer/positional-audio/link-plugin" >}})*
-
-### 3D/Game Engines With Native Support
-
-| Engine | Version | Action required | Platform | Extended support (Context, identity) |
|---|---|---|---|---|
| ioquake3 | >= commit 0ee3960225 (2008) | Set cl_useMumble to 1 | Any | No |
| Source Engine | >= ? | No | Any | Yes* |
| YEngine Next Generation (if using Y.mumble) | >= commit b4011706e7 | No | Linux | Yes |
| Game | Version | Action required | Platform | Extended support (Context, identity) |
|---|---|---|---|---|
| Age of Chivalry | Build 4104 | No | Windows | Context only |
| ArmA 2 | 1.08 while the latest is 1.10 | No | Windows | No |
| Battlefield 1 | No | Windows | Yes* | |
| Battlefield 1942 | 1.61b | No | Windows | No |
| Battlefield 2 | 1.50 | No | Windows | Yes* |
| Battlefield 2142 | 1.51 | No | Windows | Yes* |
| Battlefield 3 | Build 1147186 - End Game DLC | No | Windows | Yes* |
| Battlefield 4 | 1.8.2.48475 | No | Windows | Yes* |
| Battlefield Bad Company 2 | Build 795745 | No | Windows | No |
| Battlefield Heroes | ? | No | Windows | No |
| Borderlands | 1.4.0 while the latest is 1.4.1 | No | Windows | Context only* |
| Borderlands 2 | 1.8.3 while the latest is 1.8.4 | No | Windows | Identity only* |
| Breach | 1.1.0 | No | Windows | No |
| Call of Duty 2 | 1.3 | No | Windows | No |
| Call of Duty 4: Modern Warfare | 1.7.568 | No | Windows | Context only* |
| Call of Duty: Modern Warfare 2 Multiplayer | 1.2.208 | No | Windows | No |
| Call of Duty: Modern Warfare 2 Special Ops | 1.1 | No | Windows | No |
| Call of Duty: World at War | 1.7.1263 | No | Windows | No |
| Counter-Strike 1.6 | 1.6 | No | Windows | Context only* |
| Dystopia | Build 4104 | No | Windows | Context only* |
| Enemy Territory: Quake Wars | 1.50 | No | Windows | Context only* |
| Final Fantasy XIV | 2016.11.11.0000.0000 | No | Windows | Yes* |
| Garry's Mod 11 | Build 5692 | No | Windows | Context only* |
| Grand Theft Auto IV | 1.0.7.0 | No | Windows | No |
| Grand Theft Auto: San Andreas | 1.0 | No | Windows | No |
| Grand Theft Auto V | 1.50 (Steam) 1.38 (Retail) | No | Windows | Identity only* |
| Guild Wars | Build 36001 | No | Windows | Partial context only* |
| Insurgency: Modern Infantry Combat | Build 4044 | No | Windows | Context only* |
| Just Cause 2 | 1.0.0.2 | No | Windows | No |
| League of Legends | 1.0.0.145 | No | Windows | Context only* |
| Left 4 Dead | 1.0.3.1 | No | Windows | Yes* |
| Left 4 Dead 2 | 2.1.4.6 | No | Windows, Linux | Yes* |
| Lord of the Rings Online | Update 4 while the latest is Update 18 | No | Windows | Partial context only* |
| Quake Live | 1069 | No | Windows | Yes* |
| Rocket League | 1.42 | No | Windows, Linux | No |
| Staxel | Any | No | Windows | Yes |
| Sub Rosa | 0.07b | No | Windows | No |
| Unreal Tournament (UT99) | 436 | No | Windows | Partial context only* |
| Unreal Tournament 2004 | Build 3369 | No | Windows | No |
| Unreal Tournament 3 | 2.1 | No | Windows | No |
| Wolfenstein: Enemy Territory | 2.60b | No | Windows | Context only* |
| World of Warcraft | 7.0.3.22810 | No | Windows | Yes* |
| Engine | Version | Action required | Platform | Extended support (Context, identity) |
|---|---|---|---|---|
| ioquake3 | >= commit 0ee3960225 (2008) | Set cl_useMumble to 1 | Any | No |
| Source Engine | >= ? | No | Any | Yes* |
| YEngine Next Generation (if using Y.mumble) | >= commit b4011706e7 | No | Linux | Yes |
| Game | Version | Action required | Platform | Extended support (Context, identity) |
|---|---|---|---|---|
| Age of Chivalry | Build 4104 | No | Windows | Context only |
| ArmA 2 | 1.08 while the latest is 1.10 | No | Windows | No |
| Battlefield 1 | No | Windows | Yes* | |
| Battlefield 1942 | 1.61b | No | Windows | No |
| Battlefield 2 | 1.50 | No | Windows | Yes* |
| Battlefield 2142 | 1.51 | No | Windows | Yes* |
| Battlefield 3 | Build 1147186 - End Game DLC | No | Windows | Yes* |
| Battlefield 4 | 1.8.2.48475 | No | Windows | Yes* |
| Battlefield Bad Company 2 | Build 795745 | No | Windows | No |
| Battlefield Heroes | ? | No | Windows | No |
| Borderlands | 1.4.0 while the latest is 1.4.1 | No | Windows | Context only* |
| Borderlands 2 | 1.8.3 while the latest is 1.8.4 | No | Windows | Identity only* |
| Breach | 1.1.0 | No | Windows | No |
| Call of Duty 2 | 1.3 | No | Windows | No |
| Call of Duty 4: Modern Warfare | 1.7.568 | No | Windows | Context only* |
| Call of Duty: Modern Warfare 2 Multiplayer | 1.2.208 | No | Windows | No |
| Call of Duty: Modern Warfare 2 Special Ops | 1.1 | No | Windows | No |
| Call of Duty: World at War | 1.7.1263 | No | Windows | No |
| Counter-Strike 1.6 | 1.6 | No | Windows | Context only* |
| Dystopia | Build 4104 | No | Windows | Context only* |
| Enemy Territory: Quake Wars | 1.50 | No | Windows | Context only* |
| Final Fantasy XIV | 2016.11.11.0000.0000 | No | Windows | Yes* |
| Garry's Mod 11 | Build 5692 | No | Windows | Context only* |
| Grand Theft Auto IV | 1.0.7.0 | No | Windows | No |
| Grand Theft Auto: San Andreas | 1.0 | No | Windows | No |
| Grand Theft Auto V | 1.50 (Steam) 1.38 (Retail) | No | Windows | Identity only* |
| Guild Wars | Build 36001 | No | Windows | Partial context only* |
| Insurgency: Modern Infantry Combat | Build 4044 | No | Windows | Context only* |
| Just Cause 2 | 1.0.0.2 | No | Windows | No |
| League of Legends | 1.0.0.145 | No | Windows | Context only* |
| Left 4 Dead | 1.0.3.1 | No | Windows | Yes* |
| Left 4 Dead 2 | 2.1.4.6 | No | Windows, Linux | Yes* |
| Lord of the Rings Online | Update 4 while the latest is Update 18 | No | Windows | Partial context only* |
| Quake Live | 1069 | No | Windows | Yes* |
| Rocket League | 1.42 | No | Windows, Linux | No |
| Staxel | Any | No | Windows | Yes |
| Sub Rosa | 0.07b | No | Windows | No |
| Unreal Tournament (UT99) | 436 | No | Windows | Partial context only* |
| Unreal Tournament 2004 | Build 3369 | No | Windows | No |
| Unreal Tournament 3 | 2.1 | No | Windows | No |
| Wolfenstein: Enemy Territory | 2.60b | No | Windows | Context only* |
| World of Warcraft | 7.0.3.22810 | No | Windows | Yes* |
[Play-Donate](https://play.google.com/store/apps/details?id=se.lublin.mumla.donation), [F-Droid](https://f-droid.org/packages/se.lublin.mumla)){{%/ content-layout/download-ext %}} +{{< content-layout/downloads >}} {{% content-layout/download-ext osclass="android" %}}Mumla +([Play](https://play.google.com/store/apps/details?id=se.lublin.mumla),
[Play-Donate](https://play.google.com/store/apps/details?id=se.lublin.mumla.donation), +[F-Droid](https://f-droid.org/packages/se.lublin.mumla)){{%/ content-layout/download-ext %}} {{< /content-layout/downloads >}} ## Development snapshots -Development snapshots contain unreleased features and changes that will eventually be available in the next stable release. Please report any problems -you encounter on [our issue tracker](https://github.com/mumble-voip/mumble/issues). +Development snapshots contain unreleased features and changes that will eventually be available in the next stable +release. Please report any problems you encounter on [our issue tracker](https://github.com/mumble-voip/mumble/issues). -The most recent snapshot version is the third release candidate for Mumble 1.5.x -([Release Announcement]({{< relref "/blog/2024-04-14-mumble-1-5-629" >}})). +The most recent snapshot version is the third release candidate for Mumble 1.5.x ([Release Announcement]({{< relref "/blog/2024-04-14-mumble-1-5-629" >}})). -Note that we are currently not able to provide static server binaries for Linux nor are we able to provide a snapshot PPA for Linux just yet. +Note that we are currently not able to provide static server binaries for Linux nor are we able to provide a snapshot +PPA for Linux just yet. {{< content-layout/downloads >}} {{< content-layout/download name="Client for Windows (x64)" href="https://dl.mumble.info/latest/snapshot/client-windows-x64" osclass="windows">}} @@ -158,8 +165,8 @@ Note that we are currently not able to provide static server binaries for Linux {{< content-layout/download name="Server for macOS >= 10.13 (x64)" href="https://dl.mumble.info/latest/snapshot/server-macos-x64" osclass="mac">}} {{< /content-layout/downloads >}} -Note that we are no longer able to support macOS < 10.13 since [Qt does not support](https://doc.qt.io/qt-5/macos.html#supported-versions) these -versions anymore. +Note that we are no longer able to support macOS < 10.13 since +[Qt does not support](https://doc.qt.io/qt-5/macos.html#supported-versions) these versions anymore. ## Source Code @@ -167,4 +174,3 @@ As a free software project the source code is publicly readable and under a perm Our Mumble project source code is hosted on GitHub as [`mumble`](https://github.com/mumble-voip/mumble). The iOS app as [`mumble-iphoneos`](https://github.com/mumble-voip/mumble-iphoneos). - diff --git a/hugo/content/feature-requests/index.md b/hugo/content/feature-requests/index.md index b2b215f8..8a06fe60 100644 --- a/hugo/content/feature-requests/index.md +++ b/hugo/content/feature-requests/index.md @@ -1,7 +1,10 @@ ---- -title: "Mumble Feature Requests" -layout: "feature-requests" ---- -The feature requests are submitted, voted on, discussed, and managed [in our issue tracker](https://github.com/mumble-voip/mumble/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc+). - -Don’t see a feature request for something that you would love to see? [Create a new feature request for it!](https://github.com/mumble-voip/mumble/issues/new?assignees=&labels=&template=feature_request.md&title=) +--- +title: "Mumble Feature Requests" +layout: "feature-requests" +--- + +The feature requests are submitted, voted on, discussed, and managed +[in our issue tracker](https://github.com/mumble-voip/mumble/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc+). + +Don’t see a feature request for something that you would love to see? +[Create a new feature request for it!](https://github.com/mumble-voip/mumble/issues/new?assignees=&labels=&template=feature_request.md&title=) diff --git a/hugo/content/privacy.md b/hugo/content/privacy.md index a97237fb..0413745e 100644 --- a/hugo/content/privacy.md +++ b/hugo/content/privacy.md @@ -1,41 +1,53 @@ --- title: Privacy --- + This privacy policy describes our various services and products and how we handle data within their context. ## This Website at `www.mumble.info` The webserver may log non-person specific information. -As the website itself has no form of user input, we do not handle any user and personal information beyond simple and non-associated access logging. +As the website itself has no form of user input, we do not handle any user and personal information beyond simple and +non-associated access logging. -Contributors to the website source code (content and technical) contributors will committed to the source code history in the form the contributor submits. be shown as such under the names they identify themselves as and contribute as. Contributors may be shown on individual webpages for attribution. +Contributors to the website source code (content and technical) contributors will committed to the source code history +in the form the contributor submits. be shown as such under the names they identify themselves as and contribute as. +Contributors may be shown on individual webpages for attribution. ## The Documentation Wiki at `wiki.mumble.info` -The Mumble documentation wiki makes use of Google Analytics for website usage statistics. A cookie with name `_ga` specific to our domain is used for tracking. Please refer to [this Google page for more information](https://support.google.com/analytics/answer/6004245). +The Mumble documentation wiki makes use of Google Analytics for website usage statistics. A cookie with name `_ga` +specific to our domain is used for tracking. Please refer to +[this Google page for more information](https://support.google.com/analytics/answer/6004245). The webserver may log non-person specific information. -Users registering and account and making changes to the wiki content will do so under the specified name, account and license. They will be listed in a pages history as a contributor along with their contribution. +Users registering and account and making changes to the wiki content will do so under the specified name, account and +license. They will be listed in a pages history as a contributor along with their contribution. ## Mumble Client ### Optional Anonymous Usage Statistics -When a user decides to support us by submitting anonymous usage statistics some general usage and environment information will be sent to us. This includes operating system, ip address (for country information), Mumble version, and some other information. For the current specifics the client source code can be inspected. +When a user decides to support us by submitting anonymous usage statistics some general usage and environment +information will be sent to us. This includes operating system, ip address (for country information), Mumble version, +and some other information. For the current specifics the client source code can be inspected. ### Optional Update Checks -If enabled the client will automatically check for available application updates. It will only send the required information to be able to do so: the application version and the operating system/type of application. +If enabled the client will automatically check for available application updates. It will only send the required +information to be able to do so: the application version and the operating system/type of application. -If enabled the positional audio plugin and overlay update check will send the corresponding version and operating system type in a similar fashion for this purpose. +If enabled the positional audio plugin and overlay update check will send the corresponding version and operating system +type in a similar fashion for this purpose. The settings are located in the client applications settings dialog: Settings ➡ Network ➡ Privacy section. ### Public Server List -When opening the public server list in the connect dialog, the client will request this list from our server. Only the data required for doing so is sent. +When opening the public server list in the connect dialog, the client will request this list from our server. Only the +data required for doing so is sent. This functionality can be disabled through a hidden configuration setting (not visible in the user interface). @@ -43,14 +55,19 @@ This functionality can be disabled through a hidden configuration setting (not v While this is not data being sent to us we want to mention this for completeness. -When you see servers listed in the connect dialog a “ping” request packet will be sent to it in order to display the ping (connection latency) and user count as you will see them in the user interface. +When you see servers listed in the connect dialog a “ping” request packet will be sent to it in order to display the +ping (connection latency) and user count as you will see them in the user interface. -When connecting to a server the technically required data is sent to and received from the server. Please refer to the server providers privacy policy for details. +When connecting to a server the technically required data is sent to and received from the server. Please refer to the +server providers privacy policy for details. -The user can prevent sending OS information to servers they connect to in the Settings ➡ Network ➡ Privacy section; Do not send OS information to Mumble and web servers. +The user can prevent sending OS information to servers they connect to in the Settings ➡ Network ➡ Privacy section; Do +not send OS information to Mumble and web servers. ## Mumble Server (previously called “Murmur”) -When the server is configured to register with our public server list ([`register*` settings][1]) the configured or automatically determined information (as described in the configuration documentation) is sent to us and consequently being listed publicly on our public server list. +When the server is configured to register with our public server list ([`register*` settings][1]) the configured or +automatically determined information (as described in the configuration documentation) is sent to us and consequently +being listed publicly on our public server list. - [1]: https://wiki.mumble.info/wiki/Murmur.ini#Server_Registration +[1]: https://wiki.mumble.info/wiki/Murmur.ini#Server_Registration diff --git a/hugo/content/security/Mumble-SA-2014-001.md b/hugo/content/security/Mumble-SA-2014-001.md index 525bfd1e..ec3f1d87 100644 --- a/hugo/content/security/Mumble-SA-2014-001.md +++ b/hugo/content/security/Mumble-SA-2014-001.md @@ -3,23 +3,25 @@ title: Mumble Security Advisory 2014-001 date: 2016-01-10 --- -ID: Mumble-SA-2014-001 ([txt](../Mumble-SA-2014-001.txt), [sig](../Mumble-SA-2014-001.txt.sig), [Blog post](/blog/mumble-1.2.5/)) +ID: Mumble-SA-2014-001 ([txt](../Mumble-SA-2014-001.txt), [sig](../Mumble-SA-2014-001.txt.sig), +[Blog post](/blog/mumble-1.2.5/)) -Date: February 2014 +Date: February 2014 -CVE Reference: CVE-2014-0044 +CVE Reference: CVE-2014-0044 -Product: Mumble +Product: Mumble -Mumble Website: http://mumble.info +Mumble Website: http://mumble.info -Permalink: http://mumble.info/security/Mumble-SA-2014-001.txt +Permalink: http://mumble.info/security/Mumble-SA-2014-001.txt -Last Updated: 05-02-2014 +Last Updated: 05-02-2014 ## Vulnerability -A malformed Opus voice packet sent to a Mumble client could trigger a NULL pointer dereference or an out-of-bounds array access, leading to a crash (Denial of Service). +A malformed Opus voice packet sent to a Mumble client could trigger a NULL pointer dereference or an out-of-bounds array +access, leading to a crash (Denial of Service). This can be triggered remotely by an entity participating in a Mumble voice chat. @@ -27,41 +29,59 @@ This can be triggered remotely by an entity participating in a Mumble voice chat Mumble 1.2.4 in its default configuration is vulnerable. This is the only stable release that is vulnerable. -Pre-release snapshots released prior to 1.2.4 (these are named 1.2.3-