Valhalla Legends Archive

Ribose#1243

Quote from: MysT_DooM on August 14, 2011, 04:48 PM
im kinda of a big deal on the internet

+1

Do you seriously not understand why your topic is trash?

...

You can't do that with xsha1 or especially sha1 (except by making a table with all possible passwords leading to all possible results). That's the point of a hashing algorithm...

Quote from: JayTee on May 15, 2011, 05:34 AM
- Version: 0D 00 00 00 (differs from documentation - surely because of the new patch ?!)

Since the verbyte at the time of that post was 0x0B and now it's 0x0D, it's obviously the verbyte (the same one you need to log on). If you didn't realize that from the post you linked to, you should probably stop...

I've never worked with D2GS so I couldn't tell you where that data comes from, but I just wanted to answer that part for you.

Can has SC2 for mah lower-end lappy? xD

What's it like?

Find a newer language that suits your needs. VB6 isn't sold because it's old.

... after six years? An eternity on the Internet.

From what I've seen, the ladder byte (which is stored in the 31st byte of the statstring data, when character name, realm name, and the commas are removed, or in the MCP character data string) is a number < 255, which is the ladder season number, or 255 (0xFF), meaning started non-ladder.

Here, I'll look at your packet:

Quote
?? ?? - you lost the packet length WORD when you pasted this...
19 - packet id, MCP_CHARLIST2
08 00 - requested, 8
03 00 - on this account, 3
00 00 - 0
03 00 - returned, 3
0c 56 e1 48 - expire
65 7a 6c 65 6a 61 72 74 00 - character name, "ezlejart"
84 80 ff ff ff ff ff ff ff ff ff ff ff 05 ff ff ff ff ff ff ff ff ff ff ff 01 e1 80 80 80 ff ff ff 00 - data string
5e 70 4f 4a - expire
65 66 69 72 65 75 68 67 77 69 6b 68 65 77 72 00 - character name, "efireuhgwikhewr"
84 80 ff ff ff ff ff ff ff ff ff ff ff 05 ff ff ff ff ff ff ff ff ff ff ff 01 a1 80 80 80 ff ff ff 00 - data string
66 70 4f 4a - expire
66 65 77 6b 71 6a 66 68 62 67 6c 6b 6a 65 72 00 - character name, "fewkqjfhbglkjer"
84 80 ff ff ff ff ff ff ff ff ff ff ff 05 ff ff ff ff ff ff ff ff ff ff ff 01 e1 80 80 80 05 ff ff 00 - data string

The ladder byte (#31, yellow) says that the first two are non-ladder and the third is ladder (season 5).
I looked more, and the flags byte (#27, red) has the ladder flag (0x40) OR'd on there for both characters that the program is reporting as ladder.
So I have to conclude, the flags byte (#27) contains all of the flags you provided on creating your character (ladder - 0x40, expansion - 0x20, hardcore - 0x04), and doesn't change when ladder is reset.
The ladder byte (#31), contains the ladder season number (currently 5) or 0xFF for non-ladder, and is set to 0xFF when ladder resets.

So, that program needs to be updated to check the ladder byte and not the flag byte for current ladder status, instead of returning what the character was originally created on.

So, everyone knows the normal keys:

QuoteUser Profiles:
    profile\sex
    profile\age
    profile\location
    profile\description
Account Info:
    System\Account Created
    System\Last Logon
    System\Last Logoff
    System\Time Logged
Record:
    record\GAME\#\wins
    record\GAME\#\losses
    record\GAME\#\disconnects
    record\GAME\#\last GAME
    record\GAME\#\last GAME result
    record\GAME\#\rating
    record\GAME\#\high rating
    DynKey\GAME\#\rank

where "GAME" = the four letter game code, and "#" = 0 (normal), 1 (ladder), and 3 (W2BN ironman)

Sixen says:

Quote*SystemUsername
*SystemAuthLevel
*SystemLeague
*SystemIcon
*SystemMFT Bytes
*SystemMFT Last Write
*SystemMFT Time Logged
*SystemIP
*SystemPort
*SystemFriends
*SystemFlags

which I assume is

QuoteSystem\Username
System\AuthLevel
System\League
System\Icon
System\MFT Bytes
System\MFT Last Write
System\MFT Time Logged
System\IP
System\Port
System\Friends
System\Flags

But all of Sixen's keys except "System\Username" returns an empty string.
So my question is, does anyone know any more user data keys that Battle.net stores? And for Sixen, how come those keys (except "System\Username") don't work?

yay!... LOL

IIRC it's just standard CRC32. I just implemented the first google result of C# CRC32 when I did it...

Edit: Oh yeah, you have to append stuff but the code just ends up being like:int result = Crc32.Calculate(password + servercode.ToString("X").ToUpper().PadLeft(8, '0'));

I've converted it to C# already and the hardest part is the init and 0x05 calls, not really the cryptography algorithms (since they're already in System.Security.Cryptography anyway).

Why have a separate BNLS username/password for this? Use the BNLS_AUTHORIZE and BNLS_AUTHORIZEPROOF support for that stuff... besides then you're not sending a decrypted password...

Diablo Retail (DRTL) works perfectly fine as far as I know and testing confirms that I can even use the 0x65 friend list for quick monitoring... *cough*