Valhalla Legends Archive

I felt like posting this here for the lulz. It's interesting to spoof a -1ms and 0ms ping on the actual client without using a proxy at all.

You'll need to get WPE pro if you want to do this.

WPE filter for 0ms and -1ms ping: http://dl.dropbox.com/u/13099063/0ms%20and%20-1ms%20ping%20filters.flt

There are a couple filters here. If you want 0ms ping, tick both filters. For a -1 ping, simply choose the second filter.

The reason for both is because the first part of spoofing 0ms requires me to set the length WORD of packet 0x50 from 0x3A to 0x32. I then replace the last 9 bytes with a null, followed by a SID_PING packet whose DWORD value is 0. This is supposed to prevent Battle.Net from sending another SID_PING packet, right? It actually does send me that packet... That's where the -1 filter comes in. Instead of blocking the client from replying (this actually prevents logging in), I tell the client to replace the reply with two SID_NULL packets.

Uh, packet buffer? You'll need functions for inserting/extracting different types of data into/from the packet.

Essentially, you would dump the valid part of the data (past header) into the packet handler, and then extract data from that.

What's the reason you guys disbanded [vL]? It'd be nice to see you guys on bnet, other than the freenode IRC channel that some of you hang out in.

Spread the community out further!

Quote from: MyndFyre[vL] on April 14, 2009, 03:07 PM

Quote from: vector on April 14, 2009, 02:43 PM
I think that is a win. Look at the GUI... its like windows 3.1...

Windows 95 or newer.  3.1 didn't have the "X" in the top right - it only had minimize and maximize/restore.  (Except Encarta 95, if memory serves, which ported the Win95 look to 3.1).

In referring to windows 3.1 I meant the bar below the tool bar, with the buttons on it. That design was common on windows 3.1, where you didn't really have buttons with very good graphics, and the borders for those buttons stood out. That's where I was coming from. I know the toolbar is win9x+, but those buttons look awefully old. Well, really old windows 95 programs had the same design, so meh.

I guess I'm really referring to applications (for example) like the old paint program.

@anyone: Anybody remember Knowledge Adventure '95?

lol @ 11.

I think that is a win. Look at the GUI... its like windows 3.1...

Also, Blizzard went on a huge banning spree. All of the cd-keys  I used for my bots got banned. The D3scene keys are all banned, etc.

Anyone else experience anything similar?

A couple accounts that belonged to two friends of mine "seemed" to have been hijacked by a bot application, because whenever one of them signs on, they'll usually message me with some porn site with the words like "want to see me naked?"

Usually, it'll say it automatically, but sometimes I'll just click the name, and start talking. Next thing I know, it gives me some spam message. The other account belonged to this girl I knew in high school. About a month ago, I decided to talk to her, but I guess she was afk. Weeks later, I get a message from her, but turns out it was just another of those spam posts.

This was on MSN. The only logical explanation was that both accounts were hijacked. Mine has never been hijacked, and I'm glad that it hasn't.

I know its been dead, but I would like to pick up the banner.

Could I get the program that ClanGnome runs on? I realize this may be a stupid question.

In your packet buffer, place an AddChat after each packet is about to be sent.

Ex:


Private Sub SendPacker(ByVal PacketID As Byte)
  AddChat vbYellow, "Send packet 0x" & Hex(ID)
...
End Sub


Something like that.

What part in the login sequence does the bot fail? It would be helpful to know this information, as you can pinpoint which part battle.net changed.

Which reminds me. I would like a working source of CheckRevision.dll, and the latest BNCSUtil.dll.

Thanks.

Lol, that sounds like a MITM attack, but completely different concept, as there is no middle man involved.

As Andy said the client is disconnected from BNET once he leaves chat. I've been ghosted plenty times on Warcraft 3 to know that it also happens on there as well.

Why would modifying a packet prevent the client from properly logging off of battle.net?

...

That's not going to happen, anyway.

The beta. It used to be a constant 0x05, but now the IDs are different each time.

It's really weird.