WAR3 CDKey Owner Packet

[WiLD]

Just recently got back into bnet but my question is...

...what packet am i looking at to register the cdkey? ("This cdkey is already inuse by ......")

I'm using BNLS.



I also forgot the link to Bnet Docs, anyone want to remind me?
Does Bnet Docs include documentation for BNLS or is there another place for that? Im just wondering on a certain packet.

Thanks ^^

[Sorc.Polgara]

It's sent in SID_AUTH_CHECK (0x51).

[WiLD]

Oh fair enough. For some reason i thought it was different with WAR3.

Thanks~

[WiLD]

Im getting 'invaild version' back on 0x51 (WAR3).

Im sending;

Code Select Expand


Private Sub packx51()
    InsertDWORD GTC
    InsertDWORD Version
    InsertDWORD Checksum
    If sXpan Then
        InsertDWORD &H2
    Else
        InsertDWORD &H1
    End If
    InsertDWORD &H0
    InsertNonNTString CdkeyHash
    If sXpan Then
        InsertNonNTString Cdkey2Hash
    End If
    InsertNTString exeinfo
    InsertNTString strUser
    sendPacket &H51


[Hdx]

Packet log please? We sorta need to know what info your sending.
But your format seems correct.
~-~(HDX)~-~

[Ringo]

Just recently got back into bnet but my question is...

Im getting 'invaild version' back on 0x51 (WAR3).

Game binarys maybe out of date? (im pritty sure w3 patched a few month or so ago)

[WiLD]

Packet log please? We sorta need to know what info your sending.
But your format seems correct.
~-~(HDX)~-~

Log file
(/me has no idea   O.o)

[l2k-Shadow]

Interesting, your 0x51 looks OK, only thing I can see now is the fact that BNLS is sending you outdated data. Maybe try using a local hashing library.. it's way more reliable, you don't have to rely on BNLS to update every time there is a new version of the game you are connecting to... BNCSUtil is an excellent hashing library.

[Hdx]

No...
Hes sending the wrong verbyte

                                               ff 50 3a 00 00 00 00 00 36            P:.....6
0040   38 58 49 33 52 41 57 0f 00 00 00 00 00 00 00 00  8XI3RAW.........
0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55  ...............U
0060   53 41 00 55 6e 69 74 65 64 20 53 74 61 74 65 73  SA.United States
0070   00 ff 25 08 00 00 00 00 00                       ..%......

Your not handeling 0x10 BNLS_REQUESTVERSIONBYTE properly
the current VB is 0x14 witch BNLS is sending you.

BTW, its annoying to have other connections in the log so everyone, for jsut this connection in the log use the following filter:

Code Select Expand

(tcp.port == 1622 and tcp.port == 9367) and (tcp.port == 1623 and tcp.port == 6112) and tcp.len > 0 and tcp.len != 34
~-~(HDX)~-~

[l2k-Shadow]

No...
Hes sending the wrong verbyte

ff 50 3a 00 00 00 00 00 36            P:.....6
0040   38 58 49 33 52 41 57 0f 00 00 00 00 00 00 00 00  8XI3RAW.........
0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55  ...............U
0060   53 41 00 55 6e 69 74 65 64 20 53 74 61 74 65 73  SA.United States
0070   00 ff 25 08 00 00 00 00 00                       ..%......

Your not handeling 0x10 BNLS_REQUESTVERSIONBYTE properly
the current VB is 0x14 witch BNLS is sending you.

BTW, its annoying to have other connections in the log so everyone, for jsut this connection in the log use the following filter:

Code Select Expand

(tcp.port == 1622 and tcp.port == 9367) and (tcp.port == 1623 and tcp.port == 6112) and tcp.len > 0 and tcp.len != 34
~-~(HDX)~-~

ah lol i didn't check that packet =/

[WiLD]

No...
Hes sending the wrong verbyte

                                               ff 50 3a 00 00 00 00 00 36            P:.....6
0040   38 58 49 33 52 41 57 0f 00 00 00 00 00 00 00 00  8XI3RAW.........
0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55  ...............U
0060   53 41 00 55 6e 69 74 65 64 20 53 74 61 74 65 73  SA.United States
0070   00 ff 25 08 00 00 00 00 00                       ..%......

Your not handeling 0x10 BNLS_REQUESTVERSIONBYTE properly
the current VB is 0x14 witch BNLS is sending you.

BTW, its annoying to have other connections in the log so everyone, for jsut this connection in the log use the following filter:

Code Select Expand

(tcp.port == 1622 and tcp.port == 9367) and (tcp.port == 1623 and tcp.port == 6112) and tcp.len > 0 and tcp.len != 34
~-~(HDX)~-~

Ahh i found it now! I hardcoded an old verbyte eariler but totally forgot about it.
I was looking for an effective filter, thats for that one.

Well all is working fine so i have moved onto 0x52 and after looking at Bnet Docs im stuck on;

Code Select Expand


(BYTE[32]) Salt (s)
(BYTE[32]) Verifier (v)
(STRING) Username

So what are the two bytes exactly?
Also dont you have to include the password?

[Hdx]

the s/v are the password
these should be of some help:
http://www.javaop.com/~iago/SRP.html

BNLS_CHOOSENLSREVISION
BNLS_LOGONCHALANGE
BNLS_LOGONPROOF
BNLS_CREATEACCOUNT

Oh and the ever wonderfull BNLS Protocol Specifications

Lear to readup boyo!
Have fun.
Should be more then enuf to get you going ont eh next few packets.
~-~(HDX)~-~