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.Quote:
So clientless botting is completely traceable?
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 bitch,like the damn packet changes for RB char. had me stumped for A while till somone explained what the problem was and why I kept getting jailed.Quote:
And a SHIT LOAD of time.
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.Quote:
Okay, I'll try to explain it more clear.
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.
Thank you for the clarification. I suspected this but just wanted verification.Quote:
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.