Cracked with guid

Printable View

3rd June 2015, 07:00
qwrtyp

[COD2] Cracked with guid

hi,

i found some "cracked" servers in Argentina showing a guid for players. (different guid)
Usually cracked servers do not show any guid. (guid = 0). I wanna know how to make same thing in my server.

Server ip: 190.112.0.49:28951

*the GUID is the same in other servers from this company.
3rd June 2015, 07:27
Mitch

Is the same or different than the cracked options below?

http://killtube.org/showthread.php?1...he-master-list
http://killtube.org/showthread.php?1...ull=1#post9551

Edit: both give players with a valid key (and not in use) their guid (like on non-cracked servers).
3rd June 2015, 07:49
qwrtyp

1 Attachment(s)

I think it's different because I tested with my original cd key, it appeared a "fake" guid.
then tested with a cd key pirate, came another guid (probably fake too).
Attachment 858 thats not my real guid

i already tested the method who appears real guid for original players, and zero guid for cracked players.

Edit: Another server, same guid: 190.112.0.49:28967
3rd June 2015, 08:40
Ni3ls

Thats punkbuster GUID?
3rd June 2015, 09:03
Mitch

Quote:

Originally Posted by Ni3ls

Thats punkbuster GUID?

Yes, it has something to do with your connect message. It contains a pb hash too. The server probably uses this.
Their servers are listed in the master server list. I'm assuming with a invalid key you will get a COD guid 0 (as seen in /rcon status).

Client A (to master server)

PHP Code:

ÿÿÿÿgetKeyAuthorize 0 KEYXXXXXXXXXXXXX PB aaaaaaaaaaaaaaaaaaaaaaaaaaa_hash

Your CO2 server sent this to the master server

PHP Code:

ÿÿÿÿgetIpAuthorize challenge_num_a 1.1.1.1 "fs_game" 0 PB "aaaaaaaaaaaaaaaaaaaaaaaaaaa_hash"

The master server responds with

PHP Code:

ÿÿÿÿipAuthorize challenge_num_a accept KEY_IS_GOOD 12345 master_aaaaaaaaaaaaaaaaaaaa_hash

Client B

PHP Code:

ÿÿÿÿgetKeyAuthorize 0 KEYXXXXXXXXXXXXX PB bbbbbbbbbbbbbbbbbbbbbbbbbbb_hash ÿÿÿÿgetIpAuthorize challenge_num_b 1.1.1.2 "fs_game" 0 PB "bbbbbbbbbbbbbbbbbbbbbbbbbbb_hash" ÿÿÿÿipAuthorize challenge_num_b deny INVALID_CDKEY 0 master_bbbbbbbbbbbbbbbbbbbb_hash

* 'aaaaaaaaaaaaaaaaaaaaaaaaaaa_hash' is your client pb hash and 'master_bbbbbbbbbbbbbbbbbbbb_hash' is your server pb hash.
** 12345 is the player COD guid.
4th June 2015, 01:25
qwrtyp

I tested more than 5 cd-keys (google, keygens), all they showed 8 digits pb guid (pb_plist).
4th June 2015, 06:21
Mitch

Quote:

Originally Posted by qwrtyp

I tested more than 5 cd-keys (google, keygens), all they showed 8 digits pb guid (pb_plist).

Try this:
Join with one of those keys and save the pb guid and now reconnect. Also save this pb guid.
With key that isn't in use the guid should be the same.
In this case, you should be getting 2 different pb guids.
4th June 2015, 20:13
qwrtyp

I tried
With my original cd-key and others too, always the same pb guid for each key.
server cracked always showing 8 digits pb guid... i'm curious because never seen this before

* my real pb guid is: adaa4c24, but in this server my pb guid is 568ad2c6 ever