mirror of
https://github.com/mumble-voip/mumble.git
synced 2025-10-26 11:19:16 +00:00
Mumble is an open-source, low-latency, high quality voice chat software.
audioclientcmakecross-platformgaminghacktoberfestlinuxmacosopen-sourcequality-voice-chatservervoicechatvoipwindows
We upstreamed a patch for adding the self-explanatory QSsl::TlsV1_0OrLater, QSsl::TlsV1_1OrLater and QSsl::TlsV1_2OrLater enums to QSsl. Before this, we had a patch in our Qt 5.4 build (on Windows), that changed the meaning of QSsl::TlsV1_0 to mean "TLSv1.0 or later". However, that approach wouldn't work in the real world (some setups require very specific TLS versions), so it was dropped in favour of the TlsV1_0OrLater and friends. Since our patch is in Qt 5.5, it means that we now can use QSsl::TlsV1_0OrLater in the Mumble tree (ifdef'd to QT_VERSION >= 0x050500), and not break anything for distros. For Qt 5.4, we can rely on QSsl::SecureProtocols, because Qt 5.4 deprecated SSLv3. Thus, in Qt 5.4, QSsl::SecureProtocols means the same thing as TlsV1_0OrLater means in Qt 5.5. Why do we need TlsV1_0OrLater and friends if we have QSsl::SecureProtocols? Because we don't have a guarantee that QSsl::SecureProtocols will keep having TLSv1.0 as its minimum version. The current Mumble protocol requires TLS 1.0. If something comes up in the future that makes us abandon TLSv1.0, we'll still handshake it. Rejection can happen at the Mumble protocol level instead, providing a better user experience. |
||
|---|---|---|
| .tx | ||
| 3rdparty | ||
| 3rdPartyLicenses | ||
| g15helper | ||
| icons | ||
| installer | ||
| macx | ||
| man | ||
| overlay | ||
| overlay_gl | ||
| plugins | ||
| samples | ||
| scripts | ||
| src | ||
| .gitignore | ||
| .gitmodules | ||
| CHANGES | ||
| compiler.pri | ||
| Doxyfile | ||
| INSTALL | ||
| LICENSE | ||
| main.pro | ||
| qt.pri | ||
| README | ||
| README.Linux | ||
| README.static.linux | ||
| README.static.osx | ||
| symbols.pri | ||
| winpaths_default.pri | ||
| winpaths_static.pri | ||
M U M B L E
A voicechat utility for gamers
http://mumble.info/
#mumble on freenode
Mumble is a voicechat program for gamers written on top of Qt and Speex.
There are two modules in Mumble; the client (mumble) and the server
(murmur). The client works on Win32/64, Linux and Mac OS X, while the
server should work on anything Qt can be installed on.
Note that when we say Win32, we mean Windows XP or newer.
Running Mumble
==============
On Windows, after installation, you should have a new Mumble folder in your
Start Menu, from which you can start Mumble.
On Mac OS X, to install Mumble, drag the application from the downloaded
disk image into your /Applications folder.
Once Mumble is launched, you need a server to connect to. Either create your
own or join a friend's.
Running Murmur on Unix-like systems
===================================
Murmur should be run from the command line, so start a shell (command prompt)
and go to wherever you installed Mumble. Run murmur as
murmurd [-supw <password>] [-ini <inifile>] [-fg] [v]
-supw Set new password for the user SuperUser, which is hardcoded to
bypass ACLs. Keep this password safe. Until you set a password,
the SuperUser is disabled. If you use this option, murmur will
set the password in the database and then exit.
-ini Use a inifile other than murmur.ini, use this to run several instances
of murmur from the same directory. Make sure each instance is using
a separate database.
-fg Run in the foreground, logging to standard output.
-v More verbose logging.
Running Murmur on Mac OS X
==========================
On Mac OS X, Murmur is available inside your Mumble application bundle. If you
copied the Mumble program into your Applications directory, you should be able
to run it by executing:
/Applications/Mumble.app/Contents/MacOS/murmurd -v -fg
in a Terminal. For more information, please see the 'Running Murmur on Unix-
like sytems' above.
To easily override the default Murmur configuration, a murmur.ini file can be placed in
your user's 'Library/Preferences/Mumble/' directory.
Example configuration files and other scripts can be found inside the Murmur
directory of the Mumble installation disk image.
Running Murmur on Win32
=======================
Doubleclick the Murmur icon to start murmur. There will be a small icon on your
taskbar from which you can view the log.
To set the superuser password, run murmur with the parameters '-supw <password>'.
Bandwidth usage
===============
Mumble will use 10-40 kbit/s outgoing, and the same incoming for each user.
So if there are 10 other users on the server with you, your incoming
bandwidth requirement will be 100-400 kbit/s if they all talk at the same time.