[PreRelease] TeamSpeak 3 Server 3.0.11.4 Beta

[Matthias B]

Hotfix release 3.0.11.4 is now available for testing.
It fixes some DoS vulnerabilities and the recent issue of clients dropping with the message "convert error".


Full changelog:

=== Server Release 3.0.11.4 24 august 2015
 - fixed DOS vulnerability
 - fixed clients dropping with "convert error"
 - added some timing logs

The pre-release is available for download here.

[Morthawt]

Please allow up to 5 seconds...

Okay, does the timer log thing have anything to do with fixing the issue where due to fluctuations in the server's clock people showing up being connected for 123456767a instead of reflecting that they have been connected for 12 hours ?

[KIDINK^]

Tested & works.

2015-08-19 22:35:01.488381|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.11.4 (2015-08-18 13:30:34)
2015-08-19 22:35:01.511890|INFO    |ServerLibPriv |   | SystemInformation: Linux 2.6.32-5-amd64 #1 SMP Fri Feb 15 15:39:52 UTC 2013 x86_64 Binary: 64bit
2015-08-19 22:35:01.597036|INFO    |DatabaseQuery |   | dbPlugin name:    MySQL plugin, (c)TeamSpeak Systems GmbH
2015-08-19 22:35:01.597130|INFO    |DatabaseQuery |   | dbPlugin version: 1
2015-08-19 22:35:02.102013|INFO    |Accounting    |   | Licensing Information
2015-08-19 22:35:02.102089|INFO    |Accounting    |   | type              : Non-profit
2015-08-19 22:35:02.102146|INFO    |Accounting    |   | starting date     : Tue Apr 21 00:00:00 2015
2015-08-19 22:35:02.102179|INFO    |Accounting    |   | ending date       : Sat Oct 24 00:00:00 2015
2015-08-19 22:35:02.102208|INFO    |Accounting    |   | max virtualservers: 10
2015-08-19 22:35:02.102235|INFO    |Accounting    |   | max slots         : 512
2015-08-19 22:35:02.765923|INFO    |              |   | Puzzle precompute time: 628
2015-08-19 22:35:02.766152|INFO    |FileManager   |   | listening on *.*.*.*:*****
2015-08-19 22:35:05.572914|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1, *.*.*.*, *.*.*.*, *.*.*.*, *.*.*.*,
2015-08-19 22:35:05.573312|INFO    |Query         |   | listening on *.*.*.*:*****
2015-08-19 22:35:06.384736|INFO    |              |   | Increased protection level to: 1
2015-08-19 22:35:30.750925|INFO    |Query         |   | query from 1 *.*.*.*:**** issued: login with account "serveradmin"(serveradmin)
2015-08-19 22:35:30.758853|INFO    |Query         |   | query from 2 *.*.*.*:**** issued: login with account "serveradmin"(serveradmin)
2015-08-19 22:35:31.476982|INFO    |Query         |   | query from 3 *.*.*.*:**** issued: login with account "serveradmin"(serveradmin)
2015-08-19 22:35:31.486403|INFO    |Query         |   | query from 4 *.*.*.*:**** issued: login with account "serveradmin"(serveradmin)
2015-08-19 22:36:10.876090|INFO    |              |   | Decreased protection level to: 0
2015-08-19 22:36:20.269109|INFO    |Query         |   | query from 5 *.*.*.*:***** issued: login with account "serveradmin"(serveradmin)
2015-08-19 22:36:23.007297|INFO    |VirtualSvrMgr |   | startServer() VirtualServer(3) started

[dante696]

Please allow up to 5 seconds...

Okay, does the timer log thing have anything to do with fixing the issue where due to fluctuations in the server's clock people showing up being connected for 123456767a instead of reflecting that they have been connected for 12 hours ?

This is not related to this release. It's additional server debug log, when some actions took to long.

A broken clock is a broken clock and can not be fixed from us.
A working clock (even when a remote server does change the time) should not issue what you toled us here.