This is not accurate at all. What you are referring to is the obsolete anti-bot system (much has changed now). Although I no longer work for ConquerAI, I can tell you that what we did in the past there were 3 types of challenges the anti-bot presented to you. Since the anti-bot had no knowledge of which player you were when you connected, you could exploit this until you got the challenge type of which you desired. I reverse engineered challenge type 1, and simply brute-forced the anti-bot until it challenged me with 1; and this is how we originally beat the system. Later on, we continued reverse engineering the rest of the sub types. However, much has changed since then and things are much more complicated now.Quote:
I'm trying to not be harsh to you, but your ignorance and refusal to quit is making that very hard. It is near impossible. Like so near impossible that you need to cut it out and get your act together. Cryptography was made to keep people out. Exchange cryptographies were made to keep people out even more. Bruteforce attack protection makes it near impossible to figure out. Their algorithm is not public, it's a custom exchange using custom algorithms on the server. In the chance that you figure out those server algorithms through their bruteforce attack protection, it would take years to figure out, given that you're an absolute genius. The only reason bots like ConquerAI have it is because they got the algorithms before the bruteforce attack protection went up. I tried telling you that in a friendly manor, but you cannot succeed at this project. Do you understand?
Look no further than the fact (correct me if I'm mistaken) Chrome requires you to use proxies to achieve more than 3 clientless. AI's up and down constantly with new changes being frequently added (in fact I know their clientless works perfectly fine, and you can have more than 3 on one IP unlike Chrome; but their cliented doesn't work) and then COG.. well.. not even going to bother saying about them, for whatever reason Dean calls something "clientless" which uses a client to initially achieve it. Brilliant.
Beating SRP6a was a cake walk compared to any of that though, if you can't figure out SRP6a yourself, I'd take Fang's advice and find something more productive. At least, work on something productive towards your goal such as practicing reverse engineering.