Full Version: Should we use the Teamspeak beta?
Every now and then I get a ticket or request sent my way to put the latest Teamspeak beta into Cortex. I know the new version fixes a number of vulnerabilities, but clients running the latest 'official' version can't connect to it. What do you guys think? I see plusses and minuses on both sides of adding it in.
I voted no because of the nightmare it would ensue by updating. All of my clients that are using the old version would suddenly not be able to access their server and I would get bitched at to no end.
If it was put up as a seperate engine I would say yes, lets do it.
If it was put up as a seperate engine I would say yes, lets do it.
You may want to check with TS to see how long the beta will last. It may not be worth the effort to add it only to have them release the new client shortly afterwards?
QUOTE (ECF @ Feb 27 2007, 05:27 PM) 
You may want to check with TS to see how long the beta will last. It may not be worth the effort to add it only to have them release the new client shortly afterwards?
Good point. I hadn't considered that.
As Doc said I don't want to force all my end clients to go through an update right yet. I would rather have them all have to update one day when the full release comes out.
A seperate engine would nice to test it and prepare ourselves for an eventual full update.
A seperate engine would nice to test it and prepare ourselves for an eventual full update.
I agree, check to see how long the beta will last before the full release. I also agree with Doc and Creed. 
The server betas work with the current client. I have been using the betas on my server since they started and I have not had any issues with people connecting.
QUOTE
2.0.23.15
- fixed a bug which could cause runtime errors and server crashes
2.0.23.13
- fixed the char exploit which caused problems with the player context menu and banning functionalities
- fixed a memory leak issue from version before
- fixed a small TCP query bug were selected servers were un-selected after authenticating as superadmin
- limited max TCP query connections to 100
- minor fixes
2.0.23.6
- fixed a critical bug from version 2.0.23.5, that can cause a virtual server to become completely unresponsive
2.0.23.5
- Voice server now bans your IP address for 10 minutes after 4 failed login attempts to prevent UDP bruteforce attacks
- Fixed a bug where clients could create channels without a name
- Fixed a security issue with the TCP query interface where clients could use commands without authorization
2.0.23.2
- web administration interface bans your IP address for 10 minutes after 3 failed login attempts
- fixed crashes which occured on serverstop commands via HTTP or TCP queries
- fixed a bug where clients got a timeout on serverstop commands
2.0.22.3
- fixed crashes which occured on "Exception2 EIdSocketError.Host not found" events
- minor fixes
2.0.22.2
- fixed crashes which occured on msg commands via TCP queries
- channel descriptions are now limited to 1024 chars
- minor fixes
2.0.22.1
- server removes tabulator/newline chars from nicknames
- channel names are now limited to 29 chars
- channel order can't be set anymore without permission when creating a channel
- fixed crashes which occured on serverstop commands via HTTP or TCP queries
- minor fixes
2.0.21.3
- webinterface security flaw where an serveradmin could be able to stop/delete/etc other servers via webinterface.
- multiline chats will be logged on a per line basis
- fixed a bug which could cause runtime errors and server crashes
2.0.23.13
- fixed the char exploit which caused problems with the player context menu and banning functionalities
- fixed a memory leak issue from version before
- fixed a small TCP query bug were selected servers were un-selected after authenticating as superadmin
- limited max TCP query connections to 100
- minor fixes
2.0.23.6
- fixed a critical bug from version 2.0.23.5, that can cause a virtual server to become completely unresponsive
2.0.23.5
- Voice server now bans your IP address for 10 minutes after 4 failed login attempts to prevent UDP bruteforce attacks
- Fixed a bug where clients could create channels without a name
- Fixed a security issue with the TCP query interface where clients could use commands without authorization
2.0.23.2
- web administration interface bans your IP address for 10 minutes after 3 failed login attempts
- fixed crashes which occured on serverstop commands via HTTP or TCP queries
- fixed a bug where clients got a timeout on serverstop commands
2.0.22.3
- fixed crashes which occured on "Exception2 EIdSocketError.Host not found" events
- minor fixes
2.0.22.2
- fixed crashes which occured on msg commands via TCP queries
- channel descriptions are now limited to 1024 chars
- minor fixes
2.0.22.1
- server removes tabulator/newline chars from nicknames
- channel names are now limited to 29 chars
- channel order can't be set anymore without permission when creating a channel
- fixed crashes which occured on serverstop commands via HTTP or TCP queries
- minor fixes
2.0.21.3
- webinterface security flaw where an serveradmin could be able to stop/delete/etc other servers via webinterface.
- multiline chats will be logged on a per line basis
Throw up a new engine for the people that complain. I know making a new engine is more difficult than a simple engine overwrite but it would seem to please most people.
Nice change log you posted up MaydaX. They seem to be slowly getting around to making TS more secure. That is what I want to hear. I just want to know its secure. Work on making it perform better later because right now it does just fine.
If you want to keep out hackers, just don't active the http admin. That thing is a nightmare.
I also have my TCP Port and HTTP port set to non default values. Disabling HTTP admin is not an option for GSP's i'm sure.
I haven't seen required Client update for new Teamspeak Beta. I've been running with an older TS client for a while.
I have voted no..
Why have the risk of someone not able to connect to the teamspeak server when the old version is good and certainly functional. Why not upgrade when it is fully debugged and what not? Having somone not able to connect seems like a ban in my opinion, restricting people from ts when they aren't really banned is unbelievable.
Why have the risk of someone not able to connect to the teamspeak server when the old version is good and certainly functional. Why not upgrade when it is fully debugged and what not? Having somone not able to connect seems like a ban in my opinion, restricting people from ts when they aren't really banned is unbelievable.
Kevin and I have confirmed that people running OLD version of 2.0.32.60 (which is ancient) can connect, talk, ban, be SAs with latest beta. Therefore, it's probably going in ASAP.
Good news. Does the beta have a more secure http admin section? I disabled mine the first time it was compromised and have not activated it sense.
I don't think so. I've got my HTTP firewalled off.
PLEASE PLEASE update the teamspeak.. we are constantly getting hacked by the g00nz.. it is really starting to piss me off
QUOTE (fux @ Mar 12 2007, 01:37 AM)
PLEASE PLEASE update the teamspeak.. we are constantly getting hacked by the g00nz.. it is really starting to piss me off
Fux: Turn off your web admin panel off, that will help or you can try the following: Go into permissions and turn the following off for Server Admins: AdminListDBUsers, AdminSetServerPermissions, AdminEditServerType, PrivilegeGrantSA, PrivilegeRevokeSA, PrivilegeAdminPlayerRegister, PrivilegePlayerDelete, PrivilegeRegisterSelfByDefault. By turn all of those off you will be running a much more secure TS. You also should make as few accounts as possible have SA. Those that have SA should have non-standard passwords; what I mean by that is at least 8-12 characters long made up of letters, numbers, and symbols. Make sure that all the ports TS uses are not the default numbers. Try also to change your IP if you can. Nothing is bulletproof but hopefully those changes will help you.
Thankfully never had to deal with them on my TS before, though they have taken down one of our forums though. Stupid not updated phpBB forums...It was time to switch anyways. vBulletin has been a much better solution.
thanks for the info.. right now web admin is switched off... ports are changed.. logging is on..
the bastards have hit our ts server 3days in a row now.. the 2nd time i was able to fend them off... but they came again last night for revenge without even joining our ts server and banned us all.. checked the web admin and sure enough there was an account made by them.. so i guess they got in thru there.. so ive disabled it now.. should that do the trick as in without them being able to log into the web admin they cant stuff around with the server?
the bastards have hit our ts server 3days in a row now.. the 2nd time i was able to fend them off... but they came again last night for revenge without even joining our ts server and banned us all.. checked the web admin and sure enough there was an account made by them.. so i guess they got in thru there.. so ive disabled it now.. should that do the trick as in without them being able to log into the web admin they cant stuff around with the server?
hey Creed3020 little problem.. ive disabled all those permissions you said too, but now i cant edit anything else in the teamspeak web admin.. keep getting Invalid Permissions.. i've tried enabling them again in the SA permissions but just keep getting that error..
any way to get control back?
any way to get control back?
Are you using a new database?
If you have not tried it already, start with a fresh database, change your server admin password to something VERY LONG and mix in numbers with letters.
With your web admin disabled they have to have a way in. Makes me wonder if they have an account buried in your database or if someone with admin rights is causing the problem.
If you have not tried it already, start with a fresh database, change your server admin password to something VERY LONG and mix in numbers with letters.
With your web admin disabled they have to have a way in. Makes me wonder if they have an account buried in your database or if someone with admin rights is causing the problem.
QUOTE (doc @ Mar 12 2007, 11:17 AM)
Are you using a new database?
If you have not tried it already, start with a fresh database, change your server admin password to something VERY LONG and mix in numbers with letters.
With your web admin disabled they have to have a way in. Makes me wonder if they have an account buried in your database or if someone with admin rights is causing the problem.
If you have not tried it already, start with a fresh database, change your server admin password to something VERY LONG and mix in numbers with letters.
With your web admin disabled they have to have a way in. Makes me wonder if they have an account buried in your database or if someone with admin rights is causing the problem.
yer of course.. each time we got hacked i deleted it from cortex and started again.. new password 8+ characters.. but now ive locked myself out.. as in i cant give anyone at all SA because i disabled the permissions Creed3020 told me to for SA
You now can only give people SA through the web admin panel. I didn't mean to lock you out, sorry. When you add a player on the admin panel there is a box you can click to grant SA. I do all my admin work through the admin panel, it helps to keep things secure.
As Doc said it is best to start with a fresh database because they will leave accounts all across the database with access they only know of.
As Doc said it is best to start with a fresh database because they will leave accounts all across the database with access they only know of.
yer but u cant give ppl SA if u revoke it from yourself like u said in an earlier post.. unless u add it back just to give someone SA and then revoke it again..
but the thing is one of these u suggested: AdminListDBUsers, AdminSetServerPermissions, AdminEditServerType, PrivilegeGrantSA, PrivilegeRevokeSA, PrivilegeAdminPlayerRegister, PrivilegePlayerDelete, PrivilegeRegisterSelfByDefault
is blocking me out completely from doing anything i cant even give others SA.
EDIT: never mind lol, ive finally found out how to login thru superadmin
but the thing is one of these u suggested: AdminListDBUsers, AdminSetServerPermissions, AdminEditServerType, PrivilegeGrantSA, PrivilegeRevokeSA, PrivilegeAdminPlayerRegister, PrivilegePlayerDelete, PrivilegeRegisterSelfByDefault
is blocking me out completely from doing anything i cant even give others SA.
EDIT: never mind lol, ive finally found out how to login thru superadmin
QUOTE (fux @ Mar 12 2007, 09:24 PM)
yer but u cant give ppl SA if u revoke it from yourself like u said in an earlier post.. unless u add it back just to give someone SA and then revoke it again..
but the thing is one of these u suggested: AdminListDBUsers, AdminSetServerPermissions, AdminEditServerType, PrivilegeGrantSA, PrivilegeRevokeSA, PrivilegeAdminPlayerRegister, PrivilegePlayerDelete, PrivilegeRegisterSelfByDefault
is blocking me out completely from doing anything i cant even give others SA.
EDIT: never mind lol, ive finally found out how to login thru superadmin
but the thing is one of these u suggested: AdminListDBUsers, AdminSetServerPermissions, AdminEditServerType, PrivilegeGrantSA, PrivilegeRevokeSA, PrivilegeAdminPlayerRegister, PrivilegePlayerDelete, PrivilegeRegisterSelfByDefault
is blocking me out completely from doing anything i cant even give others SA.
EDIT: never mind lol, ive finally found out how to login thru superadmin
Glad you figured it out. I didn't mention that you need be to be logged in as a the superadmin, another oops on my part. That was an assumption I made on my part.
If you need any more help please ask away or send me a PM. We can always chat over TS if you want to as well.
After much deliberation we decided to go with the TS beta. This Cortex update will also take away superadmin access. That was a goof on our part, so enjoy SA while you can. 
We found a problem in Cortex's engine update routines, so we'll release the TS update after we release Cortex 1.35a.
We found a problem in Cortex's engine update routines, so we'll release the TS update after we release Cortex 1.35a.
QUOTE (klaude @ Mar 13 2007, 08:17 AM)
After much deliberation we decided to go with the TS beta. This Cortex update will also take away superadmin access. That was a goof on our part, so enjoy SA while you can. We found a problem in Cortex's engine update routines, so we'll release the TS update after we release Cortex 1.35a.
We found a problem in Cortex's engine update routines, so we'll release the TS update after we release Cortex 1.35a.About this whole lack of SA access....Do you mean no one will be able to access/login as a superadmin? If so that is kinda dumb. How are you supposed to edit certain server wide settings and such?
What do you mean as a "goof on your part"? That the update wasn't done correctly and should be fixed before it is released? or that we should have never had superadmin access?
Thanks for the update Kevin!
oh we gotta have superadmin thats how i control my server now after following the VERY helpful advice from creed!!!
You are not seriously gona use this beta are you?
If so thats a joke most of us here use super admin 24/7 .
Using this beta that clearly does not work is a complete joke tbh,fix the thing then release it!!
Also do i have to update or can i just keep it as it is until the final release is out?
If so thats a joke most of us here use super admin 24/7 .
Using this beta that clearly does not work is a complete joke tbh,fix the thing then release it!!
Also do i have to update or can i just keep it as it is until the final release is out?
All poeple must update or they will be burned at the stake.
J/K. Just don't update your TS engine.
J/K. Just don't update your TS engine.
What have you seen that doesn't work in the beta. My testing shows it works just fine.
The problem with superadmin access is folks were going in and setting up their own teamspeak servers in the superadmin panel. That rather conflicts with how Cortex sets up instances. One of the biggest issues I see with Cortex/TS support is that Cortex won't start a new TS instance because someone logged into superadmin and set up a TS server on that IP and port already. So what kind of stuff are ya'll doing with superadmin. The TS patch isn't in Cortex yet, so rather than break functionality I'll hear ya'll out.
On a complete side note, I never got the notion of saying that something you don't like "is a joke". To me a joke implies that whatever was done that you don't like was done intentionally and to try to be humorous. So when you say 'support is a joke' or 'cortex is a joke' or 'the new TS beta is a joke' i don't really get it. I'd rather folks just said something sucks than something is a joke. When I hear something is a joke I get a huge urge to end up whatever I'm doing with a punchline. That rarely helps the situation out.
The problem with superadmin access is folks were going in and setting up their own teamspeak servers in the superadmin panel. That rather conflicts with how Cortex sets up instances. One of the biggest issues I see with Cortex/TS support is that Cortex won't start a new TS instance because someone logged into superadmin and set up a TS server on that IP and port already. So what kind of stuff are ya'll doing with superadmin. The TS patch isn't in Cortex yet, so rather than break functionality I'll hear ya'll out.
On a complete side note, I never got the notion of saying that something you don't like "is a joke". To me a joke implies that whatever was done that you don't like was done intentionally and to try to be humorous. So when you say 'support is a joke' or 'cortex is a joke' or 'the new TS beta is a joke' i don't really get it. I'd rather folks just said something sucks than something is a joke. When I hear something is a joke I get a huge urge to end up whatever I'm doing with a punchline. That rarely helps the situation out.
LoL i see your point 
Anyway back to business..has this beta even passed stress testing yet?
Anyway back to business..has this beta even passed stress testing yet?
I don't want to use SA to login and create additional servers. I want SA to use SA. I don't want to be restricted in what I have access to in regards to the TS server.
I use the SA login always and never the admin login. I like to be able to set Global Settings and select my server and then go from there.
I use Cortex to run a backup of my main TS. I just regularly update the database in Cortex. The database though imports more than just one server. As the main server is really a network of various TS servers. So when I bring it into Cortex I need to delete those other servers each time. I don't want to run backups for the other servers on the network, just my own. That can only be done with SA.
I can understand how having SA access causes trouble Kevin but for me it would cause even more trouble for myself by not having it.
I use the SA login always and never the admin login. I like to be able to set Global Settings and select my server and then go from there.
I use Cortex to run a backup of my main TS. I just regularly update the database in Cortex. The database though imports more than just one server. As the main server is really a network of various TS servers. So when I bring it into Cortex I need to delete those other servers each time. I don't want to run backups for the other servers on the network, just my own. That can only be done with SA.
I can understand how having SA access causes trouble Kevin but for me it would cause even more trouble for myself by not having it.
QUOTE (OwNaGe @ Mar 14 2007, 12:27 PM)
LoL i see your point
Anyway back to business..has this beta even passed stress testing yet?
Anyway back to business..has this beta even passed stress testing yet?
Steps to find out:
1) Set one of these new BETA servers
2) Leave everything set to default values
3) Give the IP address to the g00ns
4) Sit back and watch
I don't know of any group better at bringing TS servers down.
lol
Personally I don't see a need for superadmin. If you want another server, just create one via cortex. Like Kevin said, people messing around with it usually cause more problems than anything.
QUOTE (klaude @ Mar 13 2007, 09:17 AM)
After much deliberation we decided to go with the TS beta. This Cortex update will also take away superadmin access. That was a goof on our part, so enjoy SA while you can. We found a problem in Cortex's engine update routines, so we'll release the TS update after we release Cortex 1.35a.
We found a problem in Cortex's engine update routines, so we'll release the TS update after we release Cortex 1.35a. what ya find
QUOTE (ntburchf @ Mar 14 2007, 11:56 PM)
what ya find Rabbits in DB doing damage. Lots and lots of Rabbits.
Aside from Rabbit breaking cortex databases, (much like how ntburchf used to really break his cortex database ) we found a case where the engine update routines won't properly update instance files in the Linux version of Cortex for certain engine types (Teamspeak being the only one). We've got that bug fixed in 1.35a, so we're waiting on that before releasing the TS fix.
As for the Superadmin access, suppose that I made it so only admin level users could view or edit their superadmin password. Would that work out for you guys? That'll keep your clients out of the superadmin unless you give them permission to edit admin cvars for that instance.
) we found a case where the engine update routines won't properly update instance files in the Linux version of Cortex for certain engine types (Teamspeak being the only one). We've got that bug fixed in 1.35a, so we're waiting on that before releasing the TS fix.As for the Superadmin access, suppose that I made it so only admin level users could view or edit their superadmin password. Would that work out for you guys? That'll keep your clients out of the superadmin unless you give them permission to edit admin cvars for that instance.
I think that would be much better klaude sounds good to me anyway
QUOTE (klaude @ Mar 15 2007, 08:39 AM)
Aside from Rabbit breaking cortex databases, (much like how ntburchf used to really break his cortex database ) we found a case where the engine update routines won't properly update instance files in the Linux version of Cortex for certain engine types (Teamspeak being the only one). We've got that bug fixed in 1.35a, so we're waiting on that before releasing the TS fix.
As for the Superadmin access, suppose that I made it so only admin level users could view or edit their superadmin password. Would that work out for you guys? That'll keep your clients out of the superadmin unless you give them permission to edit admin cvars for that instance.
) we found a case where the engine update routines won't properly update instance files in the Linux version of Cortex for certain engine types (Teamspeak being the only one). We've got that bug fixed in 1.35a, so we're waiting on that before releasing the TS fix.As for the Superadmin access, suppose that I made it so only admin level users could view or edit their superadmin password. Would that work out for you guys? That'll keep your clients out of the superadmin unless you give them permission to edit admin cvars for that instance.
This sounds like a workable solution for everyone involved. /me likes
QUOTE (klaude @ Mar 15 2007, 09:39 AM)
Aside from Rabbit breaking cortex databases, (much like how ntburchf used to really break his cortex database ) we found a case where the engine update routines won't properly update instance files in the Linux version of Cortex for certain engine types (Teamspeak being the only one). We've got that bug fixed in 1.35a, so we're waiting on that before releasing the TS fix.
As for the Superadmin access, suppose that I made it so only admin level users could view or edit their superadmin password. Would that work out for you guys? That'll keep your clients out of the superadmin unless you give them permission to edit admin cvars for that instance.
) we found a case where the engine update routines won't properly update instance files in the Linux version of Cortex for certain engine types (Teamspeak being the only one). We've got that bug fixed in 1.35a, so we're waiting on that before releasing the TS fix.As for the Superadmin access, suppose that I made it so only admin level users could view or edit their superadmin password. Would that work out for you guys? That'll keep your clients out of the superadmin unless you give them permission to edit admin cvars for that instance.
I never broke it, but sure found a lot of bugs with it
If anyone needs help with overwriting the server_windows.exe with the new one, let me know. I have a trick to get around Cortex and allow you to overwrite the stock exe. I have a ranked box and was not able to do it via remote desktop.
After getting hit 3 times last night by idiots, I update the exe to the latest beta. I will let you all know if it keeps out the losers.
After getting hit 3 times last night by idiots, I update the exe to the latest beta. I will let you all know if it keeps out the losers.
QUOTE (doc @ Apr 1 2007, 12:29 AM)
If anyone needs help with overwriting the server_windows.exe with the new one, let me know. I have a trick to get around Cortex and allow you to overwrite the stock exe. I have a ranked box and was not able to do it via remote desktop.
After getting hit 3 times last night by idiots, I update the exe to the latest beta. I will let you all know if it keeps out the losers.
After getting hit 3 times last night by idiots, I update the exe to the latest beta. I will let you all know if it keeps out the losers.
Define getting hit 3 times by idiots?
I found something that kept all the idiots out was going into server.ini and finding "ListPublic=1" and flipping it to ListPublic=0
Also doc, check your PMs
I had http disabled but they were hacking the database. They would come in as an admin and revoke all admin priviledges then kick everyone.
The usual idiots were the culprits.
Also no PM on TP forums. Send it via email.
The usual idiots were the culprits.
Also no PM on TP forums. Send it via email.
QUOTE (doc @ Apr 1 2007, 11:37 PM)
I had http disabled but they were hacking the database. They would come in as an admin and revoke all admin priviledges then kick everyone.
The usual idiots were the culprits.
Also no PM on TP forums. Send it via email.
The usual idiots were the culprits.
Also no PM on TP forums. Send it via email.
You got a weak passworded admin.
This board doesn't give up emails and won't let you send them from the board. PMs work, drop your email into a PM for me.
Bumpabump!
The latest TS beta is in Cortex now.
The latest TS beta is in Cortex now.
QUOTE (klaude @ May 17 2007, 12:37 AM)
Bumpabump!
The latest TS beta is in Cortex now.
The latest TS beta is in Cortex now.
Major issues now on teamspeak after update with running multipal instances , now only one instance will come up and it has all the wrong info. on it . Also gives me two differnt errors
Attempted connection to Teamspeak@67.18.131.???:8767 failed.
Teamspeak@67.18.131.???:51234: ERROR, invalid login
Ok after rereading the news I figured it out if you have put in a differnt superadmin then the default you will have to put in the password for it also on the config .
QUOTE (CLINTON @ May 17 2007, 08:58 AM)
Major issues now on teamspeak after update with running multipal instances , now only one instance will come up and it has all the wrong info. on it . Also gives me two differnt errors
Attempted connection to Teamspeak@67.18.131.???:8767 failed.
Teamspeak@67.18.131.???:51234: ERROR, invalid login
Ok after rereading the news I figured it out if you have put in a differnt superadmin then the default you will have to put in the password for it also on the config .
Attempted connection to Teamspeak@67.18.131.???:8767 failed.
Teamspeak@67.18.131.???:51234: ERROR, invalid login
Ok after rereading the news I figured it out if you have put in a differnt superadmin then the default you will have to put in the password for it also on the config .
Whew, someone actually reads the news I put in Cortex?
Yes double check your configs after applying this update. We did some housecleaning with superadmin passwords (removing dupes, making sure they're not written to files, etc).
QUOTE (klaude @ May 17 2007, 11:50 AM)
Whew, someone actually reads the news I put in Cortex? Yes double check your configs after applying this update. We did some housecleaning with superadmin passwords (removing dupes, making sure they're not written to files, etc).
Yes double check your configs after applying this update. We did some housecleaning with superadmin passwords (removing dupes, making sure they're not written to files, etc).Ill say problems, big time. I unchecked registered just to try and get in my TS2 server and ended up on a client TS2 server. and nothing but errors in Cortex now.
I had a bad feeling about this update...
4055298PLNT
I'm looking into it right now. I'll post when I have more info.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.