• Welcome to Valhalla Legends Archive.
 

Seems as if Bnet's up to it again

Started by IdIm, September 12, 2006, 02:34 PM

Previous topic - Next topic
|

MyndFyre

Quote from: l)ragon on September 13, 2006, 07:44 PM
Quote from: MyndFyre[vL] on September 13, 2006, 07:41 PM
Quote from: l)ragon on September 13, 2006, 07:40 PM
Quote from: MyndFyre[vL] on September 13, 2006, 07:25 PM
Quote from: Yegg on September 13, 2006, 06:25 PM
I didn't say to return an index of where the character lies. I said to return the digit itself. So
where s = 'ver-IX86-0.mpq', loop until character is digit, return first digit found.
OK.  Using your pseudocode, the first digit found and returned would be 8.

Hdx was *right on the money* when he said that your plan was wrong.
Fine my bad here.
    MPQ_Id = RemoveNonNumerics(Replace(LCase(MPQName), "ix86", ""))

Wouldn't that leave the 86 in?
No that would replace the 'ix86' part of the string with ''.
Oh, I had your RemoveNonNumerics and Replace calls backwards
QuoteEvery generation of humans believed it had all the answers it needed, except for a few mysteries they assumed would be solved at any moment. And they all believed their ancestors were simplistic and deluded. What are the odds that you are the first generation of humans who will understand reality?

After 3 years, it's on the horizon.  The new JinxBot, and BN#, the managed Battle.net Client library.

Quote from: chyea on January 16, 2009, 05:05 PM
You've just located global warming.

Ersan

Lol @ the 9-post response to "HOW DO I PARSE A STRING!?!?!?11"

hdx thanks, think you could explain why it works 12% of the time?

Hdx

Quote from: Ersan on September 13, 2006, 08:12 PM
hdx thanks, think you could explain why it works 12% of the time?
This has been answered!
The files are numbered 0-7.
Thats 8 diffrent numbers.
People grabbing the number for index[8] will always get 6.
1/8 = 0.125 = 12.5%
Thats why it works 12.5% of the time!
Now quit asking and fix your bot!
~-~(HDX)~-~

Proud host of the JBLS server www.JBLS.org.
JBLS.org Status:
JBLS/BNLS Server Status

Ersan

#63
but there's no correlation between the MPQ number and when it works!

index[8] = 6??? how what where???

I fixed the MPQ# I send to BNLS but it still doesn't work, you said BNLS needs to be updated?

BNLS's response works 12.5% of the time? why is this??

Hdx

#64
Start giving us some data.
Packet logs are good.
Seperate them into working/not
And then post them so I may scour through and figure it out.
Because everything is working 100% of the time on my end.
Also, are you useing BNLS? If you are switch to my JBLS.
As you should of noticed above, I showed that BNLS indeed needs updating.
Also IX86ver#.mpq
# = Index[8]
ver-IX86-#.mpq
6 = Index[8]
# = Index[10]
~-~(HDX)~-~

Proud host of the JBLS server www.JBLS.org.
JBLS.org Status:
JBLS/BNLS Server Status

Ersan

JBLS doesn't support 0x0B, or it's got some different format for it because I remotely hash the password.

I'll start posting packet logs if you want, give me a minute.

Hdx

Private Sub Send0x0BBNLS(ByVal Pass As String)
    Dim PBuffer As New clsBuff
    With PBuffer
        .DWORD = Len(Pass)
        .DWORD = 2
        .void = LCase(Pass)
        .DWORD = ClientToken
        .DWORD = ServerToken
        .AddBNLSHeader &HB
        SendBNLS .All
    End With
    Debug.Print "[BNLS] Sent 0x0B"
End Sub

It support all BNLS packets + Client id's 9/a/b
Mind volenteering your password? I have gotten reports that it dosen't hash passwords with spacific Ex-ASCII charecters correctly. But I've never been able to test.
~-~(HDX)~-~

Proud host of the JBLS server www.JBLS.org.
JBLS.org Status:
JBLS/BNLS Server Status

Ersan

password doesn't have any unicode chars in it,

working:
0000  ff 50 66 00 00 00 00 00 42 2f 5b 63 88 d3 00 00   .Pf.....B/[c....
0010  00 20 58 7d 99 cb c6 01 76 65 72 2d 49 58 38 36   . X}....ver-IX86
0020  2d 32 2e 6d 70 71 00 42 3d 35 30 38 35 33 31 36   -2.mpq.B=5085316
0030  34 39 20 43 3d 33 30 36 33 39 36 37 36 37 20 41   49 C=306396767 A
0040  3d 31 36 38 32 34 35 34 38 33 35 20 34 20 41 3d   =1682454835 4 A=
0050  41 5e 53 20 42 3d 42 5e 43 20 43 3d 43 2d 41 20   A^S B=B^C C=C-A
0060  41 3d 41 2d 42 00                                 A=A-B.


notworking:
0000  ff 50 68 00 00 00 00 00 32 fe fa ba d6 d2 00 00   .Ph.....2.......
0010  00 20 58 7d 99 cb c6 01 76 65 72 2d 49 58 38 36   . X}....ver-IX86
0020  2d 32 2e 6d 70 71 00 41 3d 33 38 39 30 36 30 33   -2.mpq.A=3890603
0030  34 30 31 20 43 3d 32 35 34 33 33 38 35 38 31 30   401 C=2543385810
0040  20 42 3d 32 36 31 32 38 30 31 33 34 33 20 34 20    B=2612801343 4
0050  41 3d 41 5e 53 20 42 3d 42 2b 43 20 43 3d 43 2b   A=A^S B=B+C C=C+
0060  41 20 41 3d 41 2b 42 00                           A A=A+B.


Full packetlogs:
working - http://pastebin.ca/169660
notworking - http://pastebin.ca/169661

Hdx

MM, BNLS is returning the wrong data.
Use JBLS.org as your BNLS server.
~-~(HDX)~-~

Proud host of the JBLS server www.JBLS.org.
JBLS.org Status:
JBLS/BNLS Server Status

Ersan

#69
Like I said, JBLS seems to incorrectly hash my passwords.
I don't use the extended 0x0B, I just hash the password then use that response and wrap the client and server key around that hash and send 0x0B again, I may change it.

You're certain this is BNLS?

Hdx

Quote from: Ersan on September 13, 2006, 09:35 PM
You're certain this is BNLS?
Yes.
I have tested it many times with SB.
It works 100% of the time when useing JBLS, but only ~12.5% of the time with BNLS.
And do you mind volentering your pass so that I can test it?
~-~(HDX)~-~

Proud host of the JBLS server www.JBLS.org.
JBLS.org Status:
JBLS/BNLS Server Status

Skywing

An integer truncation issue has been fixed in the version check library used by BNLS, and a release has been made.

Ersan

#72
^^ that makes more sense, thx skywing.

BNCSUtil seems to have the same problem?

Spilled

Quote from: Ersan on September 13, 2006, 09:50 PM
^^ that makes more sense, thx skywing.

BNCSUtil seems to have the same problem?

I've established a starcraft connection with the updated bnetauth.dll but not with bncsutil.dll

BreW

#74
cool

now how do we fix this problem? people aren't as stupid as you think they are, its quite easy to parse a string.
lets say you do parse your strings, it still won't work. blizzard changed something else too :}

anyways, it seems that HDX fixed his password hash problem, but forgot wc3

|