What is it? botcheck or something? I cant figure out what it is.
Its a "Ping-Pong" packet.
Format is...
Short - size
Short - PacketID
Int - PlayerID
Int - PlayerID xor GetTime()
short - random(0x0,0xFFFF)
short - random(0x0,0xFFFF)
short - random(0x0,0xFFFF)
short - random(0x0,0xFFFF)
short - random(0x0,0xFFFF)
short - random(0x0,0xFFFF)
short - random(0x0,0xFFFF)
short - random(0x0,0xFFFF)
Int - Algorithm(InGameName) //OR 0x9D4B5703 //Wouldn't suggest 0x9D4B5703
Location in memory for creating the packet is 0x004AB0D1
So basicly it's the botcheck like I said from the begining? this is what behelit used for his standalone bot right?
Edit: and hey queen do you have some sort of messenger to talk in? I want to ask something
I dont use MSN anymore :/ but ill be getting a new messenger soon so i'll let you know ^^
This packet is what lets the peaple using coproxy decendant proxies d/c after loggin out with the proxy (* As some peaple may know when you d/c with a proxy your still online for about 10 seconds after you d/c unless you use /break command *)
I dont use MSN anymore :/ but ill be getting a new messenger soon so i'll let you know ^^
This packet is what lets the peaple using coproxy decendant proxies d/c after loggin out with the proxy (* As some peaple may know when you d/c with a proxy your still online for about 10 seconds after you d/c unless you use /break command *)
Thats due to poorly programmed proxy. Ive fixed that LONG ago. Its a 1 line fix.
And yet again, like caff did (if he did), I have to point out your noobiness. MSN/Windows Messenger does NOT have an exploit (most recent update). The fact that your a noob, and cant make the difference between things, does not mean that something is as you say, and may be quite the reverse. The other option, that you cant tweak something correctly, and messed up your messenger, is a different fact. After all, all those scripts u dl, half are filled with rootkits and trojans, so I wouldnt wonder your messenger ******** up.
Thats due to poorly programmed proxy. Ive fixed that LONG ago. Its a 1 line fix.
And yet again, like caff did (if he did), I have to point out your noobiness. MSN/Windows Messenger does NOT have an exploit (most recent update). The fact that your a noob, and cant make the difference between things, does not mean that something is as you say, and may be quite the reverse. The other option, that you cant tweak something correctly, and messed up your messenger, is a different fact. After all, all those scripts u dl, half are filled with rootkits and trojans, so I wouldnt wonder your messenger ******** up.
And like I pointed out to Caff PacketStorm have proven that when you go to share files with someone over MSN the two computers make a direct link meaning the other person can get your i.p. address, and from that perform simple TCP Fin scans and Vecna scans to determine how best to comprimise your computers security ^^
No, coproxy just closes the socket from Client-Server and the socket from Server-Client.
It theoretically wont disconnect until the server doesn't get a reply for the 3f4.
Thats due to poorly programmed proxy. Ive fixed that LONG ago. Its a 1 line fix.
And yet again, like caff did (if he did), I have to point out your noobiness. MSN/Windows Messenger does NOT have an exploit (most recent update). The fact that your a noob, and cant make the difference between things, does not mean that something is as you say, and may be quite the reverse. The other option, that you cant tweak something correctly, and messed up your messenger, is a different fact. After all, all those scripts u dl, half are filled with rootkits and trojans, so I wouldnt wonder your messenger ******** up.
Cause of poor programming? lol it was probably made for testing, atleast that is what I would to while in testing phase, AND it's not a dumb thing to have it there :/
