• Welcome to Valhalla Legends Archive.
 

Android 2.1 Battle.Net Chat Client?

Started by BaDDBLooD, May 09, 2010, 09:45 AM

Previous topic - Next topic

Invert

How about something that works on b.net 2 for Android? I'm also up to 2.3.3 (Nexus S).

Joe[x86]

I don't think there's been any substantial public Bnet2 research, although I'd love nothing more than to be corrected.
Quote from: brew on April 25, 2007, 07:33 PM
that made me feel like a total idiot. this entire thing was useless.

Sixen

Quote from: Joex86] link=topic=18231.msg185157#msg185157 date=1303829425]
I don't think there's been any substantial public Bnet2 research, although I'd love nothing more than to be corrected.
There hasn't.
Blizzard Tech Support/Op W@R - FallenArms
The Chat Gem Lives!
http://www.diablofans.com
http://www.sixen.org

Invert

Well...at some point in time Blizzard will migrate or work round having their older games' social features on b.net2. Now, the original b.net is just a thorn in Blizzards side and needs to be put down like an old dog.

Joe[x86]

Quote from: Invert on April 26, 2011, 05:22 PM
Well...at some point in time Blizzard will migrate or work round having their older games' social features on b.net2. Now, the original b.net is just a thorn in Blizzards side and needs to be put down like an old dog.

I'd like to see how they do this. DRTL will be particularly tricky because it has no CD-Key to add it to your BNet account and I don't think any current Blizzard employees dare touch it's codebase.

I'm putting a nickle on them taking down BNet1 and having the former gateways act as "translation proxies" (is there official term? I made that up) to take you to BNet2. If this happens I think it'll mean that nobody will research BNet2 since all the past work will suddenly be relevant again.
Quote from: brew on April 25, 2007, 07:33 PM
that made me feel like a total idiot. this entire thing was useless.

RealityRipple

They don't have to touch D1's codebase. All they have to do is create a new SNP file.

MysT_DooM

All one has to do is deobfuscate battle.net.dll so you can unencrypt all them packets.  Once you got that down, it should all be cake ;).  All the other info on the bitstream protocol for auth is public info from the WoW days and in relation to sc2, w/e was documented during sc2 beta
So pretty much the big job is that battle.net.dll and I only know of one person who fully deobfuscated that, which was a guy who went by " 'Rick " from a group called Lazytown, which was a short lived morph of a few members from two groups called teknogods and starcrack.   
Anyways, he never released it publically and has since disappeared.


vb6, something about that combination of numbers and letters is sexy