Packet 53+54

[UserLoser]

How does BNLS hash the data for packets 53/54 or does anybody else know how to do it without BNLS?

[Spht]

I am not familiar with packets 0x35 and 0x36.

[UserLoser]

I am not familiar with packets 0x35 and 0x36.

..........?

[Noodlez]

haha, you got owned.

[tA-Kane]

I've never seen 0x35 (perhaps you could show me a packetlog?), but 0x36 is...

DWORD - CDKeyStringLength
DWORD - ProductID (Not STAR/SEXP/W2BN/etc)
DWORD - CDKeyValue1
DWORD - ServerKey
DWORD - ClientKey
5 DWORDS - KeyHash

The KeyHash is generated by doing HashData of...

DWORD - ServerKey
DWORD - ClientKey
DWORD - ProductID
DWORD - CDKeyValue1
DWORD - CDKeyValue2

The server provides the Server key in one of the first packets (too lazy to look it up atm), the client key can be anything (most people do GetTickCount()).

Refer to the BNLS's GetVersionByte sequence to get the ProductID; it uses the same IDs.

You get the two CDKeyValues from decrypting the CD Key.

[Zorm]

you guys are so mean!  :-/

[UserLoser]

I've never heard/seen packet 35 either.  I do believe i said 54/53, unless they are the same which i dont think they are...

haha, you got owned.

Wtf is this supposed to mean?

[Zakath]

Hehe...good one Spht.

Because some of my friends are stumped as well, I'll spill the beans.

Convert '53' into hex. It becomes 0x35.

[Mesiah / haiseM]

Zakath, you are a fucking genious!

[Yoni]

Code Select Expand

#define SID_AUTH_ACCOUNTLOGON           (0x53)
#define SID_AUTH_ACCOUNTLOGONPROOF      (0x54)

How

Automagically.

[tA-Kane]

Way to ruin the fun, Zakath  

UserLoser, you should *always* be sure the people you're asking help from know what you're referencing to, such as decimal vs hex.

[UserLoser]

I didnt even think of that

[tA-Kane]

that's intelligent...  

*refrains from a nasty flame*

[UserLoser]

<--thinks skywing should share how to hash it

[Noodlez]

/me thinks you dont deserve the hash if you couldnt catch on to what spht said