User Profile

xpeh

(no biography information)

Id 203
Member for14 years, 11 months, 21 days
Comments made14
Documents authored0
News posted0
Packets authored0
Servers owned0

Comments

xpeh
🔎

Constants for Battle.Net 2.0
https://bitbucket.org/Greatwolf/starcrack/src/ccd08d31dc42/LaunchHelper/SRP6a.cpp

Now SRP uses 1 kbit modulus instead of 256 bit.

xpeh
🔎

Still no progress?

xpeh
🔎

What compression algorithm is used here?

Edit: nevermind.

xpeh
🔎

these IDs are listed in war3.mpq\Units\UnitData.slk

Or War3x.mpq respectively.

What should this mean?

0x00 (WID_GAMESEARCH):
        0x00000004: Banned CD-Key
xpeh
🔎

It's not defunct, Battle.Net clients still support it. So it can be used with Battle.Net emulators, or if someone uses man in the middle.

xpeh
🔎

It's not defunct, Battle.Net clients still support it. So it can be used with Battle.Net emulators, or if someone uses man in the middle.

xpeh
🔎

It's not defunct, Battle.Net clients still support it. So it can be used with Battle.Net emulators, or if someone uses man in the middle.

xpeh
🔎

Please also note that Battle.net only Unicode-encodes strings for Starcraft and Brood War.

It's a little outdated, at least Warcraft 3 uses UTF-8. In addition, unicode support in Starcraft is broken, text is always encoded/decoded using cp1252<->utf8 schema, that's why utf-8 encoded text will be broken for all OSes that don't have locale set to cp1252 (Westeuropean). Because of that, using of non-ascii symbols in converstaion between game and non-game client with non-cp1252 OS locale is impossible.

You should really add last change date to pages :)

xpeh
🔎

Battle.Net clients still support it. So it can be used with Battle.Net emulators, or if someone uses man in the middle.

xpeh
🔎

Battle.Net clients still support it. So it can be used with Battle.Net emulators, or if someone uses man in the middle.

xpeh
🔎

It's not defunct.

xpeh
🔎

Change the status, it's not defunct. It still works.

xpeh
🔎

From pvpgn:

define SERVER_CREATEACCTREPLY2_RESULT_OK 0x00000000

define SERVER_CREATEACCTREPLY2_RESULT_SHORT 0x00000001 / Username must be a minimum of 2 characters /

define SERVER_CREATEACCTREPLY2_RESULT_INVALID 0x00000002

define SERVER_CREATEACCTREPLY2_RESULT_BANNED 0x00000003

define SERVER_CREATEACCTREPLY2_RESULT_EXIST 0x00000004

define SERVER_CREATEACCTREPLY2_RESULT_LAST_CREATE_IN_PROGRESS 0x00000005

define SERVER_CREATEACCTREPLY2_RESULT_ALPHANUM 0x00000006

define SERVER_CREATEACCTREPLY2_RESULT_PUNCTUATION 0x00000007

define SERVER_CREATEACCTREPLY2_RESULT_PUNCTUATION2 0x00000008

It's funny that pvpgn itself (at least 1.8.x) only uses 3 codes: 0, 2, 4

xpeh
🔎

(DWORD) [5] Old password hash

This is completely wrong. It is not password hash, but DoubleHashPassword()

DWORD) [5] New password hash
is real password hash.

This relies to old logon system (before WAR3).