No, just more complicated. In a proxy, if you don't know what to do with a packet, the client still does. With standalone clientless botting you need to send valid responses to EVERY packet the server sends w/o any mistakes to cause tq to realize it's a fake client.
No more info on clientless botting :P It's not that hard of a thing to figure out, just requires a lot of documenting packets and yeah, like pro4never said. Sending valid replies.
No more info on clientless botting :P It's not that hard of a thing to figure out, just requires a lot of documenting packets and yeah, like pro4never said. Sending valid replies.
Bot check is fairly easy to figure out,And all the packets are pretty well out there,there are A few things that are A real *****,like the **** packet changes for RB char. had me stumped for A while till somone explained what the problem was and why I kept getting jailed.
I have a quick question. The encryption I am using comes from the code that tanelipe posted:
I've rewritten my code from scratch and ran into a small problem with the encryption. There was no need for me to modify the "initial packet" and the "authentication request" so I skipped decryption/encryption. The first would be the "authentication response" from the server. But the decryption goes wrong (wrong values).
After some fiddling, I decrypt/encrypt the "initial packet" (no modification), decrypt/encrypt the "authentication response" and the decryption works.
sorry having a bit of trouble understanding what you mean here... what initial packet? the password seed?
For the entire auth server section of the proxy you want to be using login encryption which requires no dhkey configuration or anything fancy. Simple .encrypt .decrypt functionality in most versions of it.
In your packet handler I'd suggest decrypting the packet, checking the type and modifying if necessary.
Then in your send function, re-encrypt it and you're good to go.
for the auth response you need to modify the server ip so that it will loop back and connect to you on the game server port.
If you don't modify this packet you will have to use a loader to force the game connection to loop back around.
I don't need to modify the "initial packet" and the "authentication request". So I simply relay those packets.
I receive the "authentication response" and I need to modify it so I decrypt and encrypt. I am certain I am decrypting correctly. The problem is... it gets decrypted wrong.
After fiddling around, I decrypted and encrypted the "initial packet" but didn't modify it. I simply relayed it, doing a useless decrypt/encrypt. Then the "authentication response" gets decrypted correctly.
The encryption code I am using is the one tanelipe gave me.
I don't need to modify the "initial packet" and the "authentication request". So I simply relay those packets.
I receive the "authentication response" and I need to modify it so I decrypt and encrypt. I am certain I am decrypting correctly. The problem is... it gets decrypted wrong.
After fiddling around, I decrypted and encrypted the "initial packet" but didn't modify it. I simply relayed it, doing a useless decrypt/encrypt. Then the "authentication response" gets decrypted correctly.
The encryption code I am using is the one tanelipe gave me.
You can't simply relay a packet even if you're not going to modify it, the whole encryption relies on the count of bytes decrypted/encrypted so you can't ignore some packets and try to decrypt/encrypt others.
You can't simply relay a packet even if you're not going to modify it, the whole encryption relies on the count of bytes decrypted/encrypted so you can't ignore some packets and try to decrypt/encrypt others.
Thank you for the clarification. I suspected this but just wanted verification.
Proxy geht nicht/Proxy doesn´t work 08/10/2010 - Metin2 Private Server - 0 Replies Folgendes Problem:
Squid ist installiert.
Startet anscheinend nicht richtig, funktioniert einfach nicht.
Die Meldung welche kommt, wenn man startet:
2010/08/10 17:02:26| Starting Squid Cache version 2.7.STABLE9 for i386-portbld-freebsd7.1...
2010/08/10 17:02:26| Process ID 1952
2010/08/10 17:02:26| With 11095 file descriptors available
2010/08/10 17:02:26| Using kqueue for the IO loop
4326 PROXY FIX Post All Proxy Fixes Here 11/26/2006 - CO2 Exploits, Hacks & Tools - 22 Replies post only the fixes for proxy here plz dont post original file. NO QUESTIONS PLZ. DONT ASK FOR ORIGINAL QOPROXY. just search and hope u dont get the keylogged version :P
Fix for patch4326 (not really an intentional patch for proxy. required little editing ;))
replace old ini in qoproxy folder with this one
