News
Server 3.0.0-rc1 to be released MAY 23, 2011
by Florence on May 20, 2011

Greetings,

On Monday, May 23rd 2011, TeamSpeak 3 Server 3.0.0-rc1 will be released. We are proud to announce that this is RC1 or "release candidate 1" of the TeamSpeak 3 server which represents a significant milestone in our development process, and symbolizes the result of many hours of hard work, feedback, and dedication from both our dev team and alpha testers. Hence, similar to the recently released RC1 client, the RC1 server also introduces a number of updates and changes.

A complete changelog follows:

Symbols Used:
+ Added feature or noticable improvement
- Bug fix or something removed
* Changed or Information
! Important - Take note!

=== Server Release 3.0.0-rc1 23 May 2011
! mysql users, please alter your table channel_properties and
extend the "value varchar(255)" field to varchar(8192)
! mysql users, please alter your table bans and
extend the "ban_name varchar(255)" field to varchar(2048)
! server uses now 10 database connections (sqlite and mysql)
! added new parameter "dbconnections" for defining max database
connections to use (1-100) default is 10
! i_group_auto_update_type values changed
* channel permissions got their own needed/power permissions instead
of using the group labeled ones
* renamed i_client_modify_power > i_client_permission_modify_power
i_client_needed_modify_power > i_client_needed_permission_modify_power
i_client_max_clones > i_client_max_clones_uid
+ added new parameter "disable_db_logging" which turns off logging
to database (logview commands wont work anymore)
+ added the TSDNS server to the server installer. Read the documentation in
the "tsdns" subfolder for details
+ added permissions i_channel_delete_power, i_channel_needed_delete_power
i_channel_permission_modify_power, i_channel_needed_permission_modify_power
+ added permission i_group_auto_update_max_value
+ added permissions i_client_needed_whisper_power and i_client_whisper_power
that determine who can whisper to whom
+ Added total bytes transfered by filetransfer to serverinfo, hostinfo and
server connectioninfo
+ improved permission add/delete performance
+ channelgroupaddperm, channelgroupdelperm, servergroupaddperm, servergroupdelperm added
optional parameter "continueonerror"
+ uploading and deleting of icons will be logged if filetransfer log is enabled
+ added some indexes for speedup lookups regarding servers.server_port and messages.message_flag_read
+ added permission b_virtualserver_change_template
+ serveredit and serverinfo command can be used with use 0 to modify and display
virtualserver template values (serverinfo display is different from normal output!)
+ added server property VIRTUALSERVER_HOSTBANNER_MODE:
HostBannerMode_NO_ADJUST=0
HostBannerMode_ADJUST_IGNORE_ASPECT=1
HostBannerMode_ADJUST_KEEP_ASPECT=2
- fixed bogus mysql create script for channel_properties
- default groups cant be permanent anymore
- removing double group assignements on server start
- fixed problem where multi-line client descriptions where stored in database
- fixed query gave out wrong error messages
- fixed permreset did not remove icon_id assignments
- fixed double assigned permissions where deleted completly
- fixed channelmove / channelcreate not checking b_channel_create_child and i_channel_needed_modify_power
- fixed sql parameter errors while inserting defaults.sql
- fixed not removing privilege key on channel deletion
- fixed snapshotdeploy would fail on virtualserver_max_slots / virtualserver_limit reached
- fixed not checking correct permissions for CHANNEL_FLAG_MAXFAMILYCLIENTS_UNLIMITED,
CHANNEL_FLAG_MAXFAMILYCLIENTS_INHERITED
- fixed not checking notifyregister / notifyunregister permissions
- fixed server critical while using notifyregister=server and multiple queries dropping at the same time
- fixed set channelgroup did not include channel name info in server log
- fixed create subchannel did not include parent channel info in server log
- fixed issue mac osx server uses 100% cpu
- Fixed a bug that could be triggered remotely and would cause the server to
shut down with a critical message in the log file.

Please note this server version fixes a vulnerability that could be used to shut down a TeamSpeak 3 Server remotely, causing the server to stop with a "critical" error log message. Therefore, we strongly recommend you upgrade all of your TeamSpeak 3 servers to the latest server version ASAP once it becomes available.

Thank you,

- TeamSpeak Team
« Read all News