[3.0.12 and above] Allow all client versions to connect

ehthe

Retired Staff
Contributor
Joined
Apr 26, 2015
Messages
1,029
Reaction score
896
Points
216
Linux binary, right ? Does it work on the unpatched binary
 

dedmen

TeamSpeak Developer
Contributor
Joined
Mar 28, 2016
Messages
530
Reaction score
584
Points
197

chuga2

Restricted
Joined
Jul 16, 2016
Messages
175
Reaction score
42
Points
61
Yep thats unique to my binarys... But ill include the allversions patch now.. Just redownload my release about 10 minutes from now and it should be included
Thank you :D, it's fine now?
Edit: Yeah it's fine, you're doing great ;) .
 

Zubastic

Member
Joined
Sep 13, 2015
Messages
2
Reaction score
0
Points
33
What difference between windows and lunix verions so u could only patch for linux only?
 

ehthe

Retired Staff
Contributor
Joined
Apr 26, 2015
Messages
1,029
Reaction score
896
Points
216
Well try to find and replace those values in the windows binary. You'll see what happens.
(Noone in their right mind would host a server on windows anyway :p )
 

Filiposd

Member
Joined
Dec 6, 2016
Messages
6
Reaction score
1
Points
39
He cract the licens key ? dat file ? on surce code.
I think it's programmed in cs...
tsd.pngts_server_acconting_licens_key_cracking_filiposd.png
ts3_server_cracking.png
 

Saci

Active Member
Joined
Oct 2, 2015
Messages
7
Reaction score
1
Points
75
Does Not Work on New Version of Server 3.1
 
Last edited:

ehthe

Retired Staff
Contributor
Joined
Apr 26, 2015
Messages
1,029
Reaction score
896
Points
216
Hey,

Here are the maybe updated values for server version 3.0.13.8 (not using anything above that yet)
I have yet to check if things have changed
Code:
// MIN_CLIENT_DESKTOP_VERSION
1445512488 - 28 C5 28 56
3 occurrences

// MIN_CLIENT_DESKTOP_VERSION - 1
1445512487 - 27 C5 28 56
1 occurrence

// MIN_CLIENT_MOBILE_VERSION
1407159763 -  D3 8D DF 53
3 occurrences

// MIN_CLIENT_MOBILE_VERSION - 1
1407159762 - D2 8D DF 53
3 occurrences



I should add that I haven't tested these with the original method (search & replace) so if you find more than the number of occurrences there's a problem.
EDIT : And so nothing has changed it seems

---- Automatically Merged Double Post ----

New post because I'm checking now (in a fast manner) for 3.1.0 version.
And indeed the values have changed
EDIT : oh well automerged

Code:
// MIN_CLIENT_DESKTOP_VERSION
1513163251 - F3 09 31 5A    -> 3.1.7
3 occurrences

// MIN_CLIENT_DESKTOP_VERSION - 1
1513163250 - F2 09 31 5A
1 occurrences

// MIN_CLIENT_MOBILE_VERSION
1502275280 - D0 E6 8A 59
3 occurrences

// MIN_CLIENT_MOBILE_VERSION - 1
1502275279 - CF E6 8A 59
3 occurrences

Do tell me if it works

Also for those who want to tinker a bit more : try to modify your client version (That should get you a "hacked client" error).
I had noticed a weird bug that disabled that hack check when patching the binary for allversions
This shouldn't happen as that check is somewhat necessary given how secure teamspeak's parsing is

---- Automatically Merged Double Post ----

Also remember to reset the database values
As they are reset to the binary's value (if found to be incorrect) every time the server is started.
You can do so with YaTQA
 
Last edited:

ehthe

Retired Staff
Contributor
Joined
Apr 26, 2015
Messages
1,029
Reaction score
896
Points
216
Oh so Teamspeak hardcoded an expiry date in their binaries starting with 3.1.0
How nice.
At last the patch doesn't seem to be working on 3.9.0 the connection just drops
Tested with client versions : 3.0.11 and 3.1.0.1

---- Automatically Merged Double Post ----

I think it might have to do with an new connection arg (and mode ?)
ot=1
 
Last edited:
Top