|
|
|
Message ID: |
0x51 |
| Message Name: |
SID_AUTH_CHECK
|
| Direction: |
Server -> Client (Received) |
| Used By: |
Starcraft, Starcraft Broodwar, Diablo II, Diablo II LOD, Warcraft III, Warcraft III: TFT |
Format:
Help
Hint: Field names highlighted in blue will display a definition if you hover over the text. |
(DWORD) Result
(STRING) Additional Information |
| Remarks: |
Reports success/failure on version & CD Key check.
Result:
0x000: Passed challenge
0x100: Old game version (Additional info field supplies patch MPQ filename)
0x101: Invalid version
0x102: Game version must be downgraded
(Additional info field supplies patch MPQ filename)
0x0NN: (where NN is the version code supplied in SID_AUTH_INFO): Invalid version code (note that 0x100 is not set in this case).
0x200: Invalid CD key
0x201: CD key in use (Additional info field supplies name of user)
0x202: Banned key
0x203: Wrong product
The last 4 codes also apply to the second cdkey, as indicated by a bitwise combination with 0x010. |
| Extra Info: |
The status of this information is: Public
If a patch file cannot be found, additional info is set to 'non-existant'. If either the executable size/date or the version code is wrong, the server will typically return a failure status.
More:
While doing a little research on how Battle.net autoupdates it's clients, I found that it (Starcraft, anyway) does not use the provisions of the SID_AUTH login system to tell clients which update file to download. Instead, it sends a SID_REPORTVERSION (from the previous logon system) containing the equivalent error code and the name of the patch file to download. This seems strange, and makes me think that the part of Battle.net responsible for updating clients is isolated from the part responsible for processing logon requests. If this is the case, it makes sense that that system was never updated, since it must still support legacy clients. In addition, this would explain why most Blizzard clients retain obsolete packet processing code.
|
| Related Links: |
[C>0x51] SID_AUTH_CHECK
|
|
Printable Version
|
User Comments:
Posted by Arta (Administrator) on 07/12/04 03:34 |
|
0x200 is invalid CD key (see above)
|
| #233 |
Posted by Ringo on 07/12/04 01:35 |
After getting IP banned for sending my 0x51 packet i have just wrote, i get the return 0x002
i logged these:
FF 51 09 00 00 02 00 00 00 !
|
| #231 |
Posted by UserLoser (Editor) on 24/10/04 01:59 |
|
Probably incase Blizzard really screws up on something and don't have time to fix it. If I remember correctly, one time a few years back, this happened on Diablo II after they released a 1.09 patch
|
| #220 |
Posted by raylu on 17/10/04 10:20 |
"0x102: Game version must be downgraded"
When would you need to downgrade??
|
| #218 |
Posted by Skywing (Editor) on 17/09/04 12:04 |
|
Fixed incorrect statement about the version code supplied in SID_AUTH_INFO not being checked by the server. Added note about the server sometimes returning an error status in the format 0x0NN where NN was the version code supplied in SID_AUTH_INFO.
|
| #215 |
Posted by MacBinaryBot (Editor) on 31/03/04 10:55 |
Your result DWORD is:
13 02 00 00
When you turn this into an integer, it becomes 0x213.
That means the second CD key you provided is for a different product.
|
| #160 |
Posted by FuzZ on 16/03/04 05:58 |
CDKey or Version was rejected for unknown reason.
FF 51 21 00 13 02 00 00 4F 77 4E 73 20 6F 77 6E 65 72 3A 20 53 79 73 2E 4F 70 65 72 61 74 6F 72 00
i dunno what's up with that.
|
| #155 |
Posted by UserLoser (Editor) on 31/12/03 09:00 |
BroodWar's Battle.snp:
.text:190178E4 loc_190178E4: ; CODE XREF: Parse0x51+37j
.text:190178E4 cmp eax, 102h
.text:190178E9 jnz short loc_1901795D
.text:190178EB push offset aUserMustReinst ; "user must reinstall and patch"
.text:190178F0 call sub_190023C0
.text:190178F5 add esp, 4
.text:190178F8 pop esi
.text:190178F9 add esp, 8
|
| #142 |
Posted by Arta (Administrator) on 27/02/03 03:22 |
If you're getting an invalid version error back from Battle.net when you send this, it's probably being caused by one of the following:
- Old hash files
- Incorrect version byte
- Hashing incorrect data
- Broken hashing function
|
| #33 |
|
|
|
