TeamSpeak 3.0.19.1 Client Released

[kaidinak]

=== Client Release 3.0.19.1 25 Apr 2016
+ Added polish and portugese translations
+ Added support for graylisted servers
- Fixed possible crash on weird unicode characters

The client communicates to our greylist (similar to the blackist) and informs the user in case that there is something wrong with the server.
The difference to the blacklist is, the user gets warned on each connect but still will be able to join.

(c) smartest man on teamspeak.com

 

[0x0539]

The client communicates to our greylist (similar to the blackist) and informs the user in case that there is something wrong with the server.
The difference to the blacklist is, the user gets warned on each connect but still will be able to join.

More info here: TeamSpeak Forums

 

[ehthe]

Has anyone found the greylist url ? It seems there isn't one, probably a different value returned by blacklist.teamspeak.com

 

[panteL]

Is the Crack still whitelisted when I use the tutorial on the server Crack thread? Hope it

 

[ehthe]

If you respect everything we tell you, then there is no risk running the crack.
(Well, there could be a hidden backdoor in the server binary by teamspeak )

 

[ololoev]

Very interesting update (greylist) but at this time there are no more additional info about this list

 

[Supervisor]

So... let me get back to topic and try to explain the new graylist feature and why we think it's important. The key issue with blacklisting is that we're punish the customer/user who, in most cases, has no idea that he or she is paying for a server that's not licensed properly. So our primary intention with the graylist is to inform the customer/user that something is wrong with the server... whether it's a cracked version or something else that's violating out license agreement. So instead of just preventing the TeamSpeak 3 Client from connecting, we're instead showing a (hopefully) meaningful message.

 

[freets3.ovh]

Hoo this is very bad

 

[Asphyxia]

I wonder what happens when the blacklist and greylist are ignored, does a virus break out of the binary and eat your system?

What this probably means:

1. We will have to start releasing fixed clients with an emphasis on privacy and security.
2. The server binaries will need stripping of the grey by the grey. Reporting to TeamSpeak each and every server a client goes to is sort of like... "tracking" and that is a little bit creepy, eh?

No problem guys.

 

[Kieran]

That's interesting. Still not the best way imo

Reporting to TeamSpeak each and every server a client goes to is sort of like... "tracking" and that is a little bit creepy, eh?

Yea that is kinda creepy/scary.

 

[Harrasan]

Yea that is kinda creepy/scary.

I can't imagine they're logging communication with their graylist box. Guess that would fill up the disk of that server pretty fast.



An official statement would be nice tho. Can someone ask in that thread? I don't have an account at TS.

Edit: nvm, I registered and asked for a statement.

 

[TripZZZZ]

Yeah they don't track servers you connect to although they have mentioned in that grey list thread on teamspeak forums that they have features that may stop illegal servers. Also they ignored the statement saying "Why don't the teamspeak team do anything when they know people used cracked lic". Plus Dante can't spell for shit.

 

[ehthe]

they don't track servers you connect to

Well they certainly could do so. Every connection a ts servers sends its ip to blacklist.teamspeak.com

 

[Asphyxia]

Well they certainly could do so. Every connection a ts servers sends its ip to blacklist.teamspeak.com

Exactly, pretty much how it works:

A client is trying to connect to a server, that client's IP address is going over to TeamSpeak's server(s). TeamSpeak may easily log the IP addresses of people using their software both client/server. That is tracking, tracking is an invasion of privacy and that is creepy.

The only thing we rely on is trusting the integrity of TeamSpeak to not track users, we will never know. We can of course monitor traffic/bandwidth and filter out their servers, block the addresses although this would be required on both the server and client for proper anonymity.

That's what happens when you use proprietary software that has licenses though, I do suppose. I think there needs to be a push for something closer to Mumble that works more like TeamSpeak (nicer interface, extra features) --- without all the security vulnerabilities, licensing/tracking and.. probably less QT with more mobile/web support for free. Definitely not centralized like Discord.

 

[Harrasan]

Since SCP said they're not tracking, I'm going to believe it. That guys response seems legit and honest. But on the other hand: what would be the benefit of tracking? I can't think of a use-case where TS could use the data in a useful way. The usual purpose of tracking is advertising. But there's no ad in the client/server.

Finding cracked servers maybe, but I think a number of connections to an ip does not necessarily mean a server is cracked or not licensed. So I don't think they can do that as it would require manual checking.

 

[TripZZZZ]

Yeah that would be one of the big questions, teamspeak claim they are developing new features to stop this happening is there a chance that they could fully stop cracked server hosting?

 

[Qraktzyl]

Yeah that would be one of the big questions, teamspeak claim they are developing new features to stop this happening is there a chance that they could fully stop cracked server hosting?

It takes them 5 days to release hotfixes for critical exploits that could crash servers.
Maybe next time Halley's comet is visible from earth (In 2061).

 

[BoTz]

----

 

[panteL]

i've got rekt laff,

That message xD

Spoiler

das ergibt nicht mal Sinn haha

 

[freets3.ovh]

fuuu
me too all my ip is banned