Quote:
Originally Posted by ntKid
This is a very nice job, since they are using HTTPS i did not even bother to replicate it because i know the hard work that it takes.
Respect for your socket knowledge^^
Keep up the good work.
|
Actually, the token is INSIDE the URL :P
it's like that in all AeriaGames' games.
you send normal HTTP request to a URL like this one, depending on your game:

this request should be a GET request.
Then you just need to keep the cookies and make another HTTP request to something like:

again, depending on the game.
This one is a POST request, with login and password in the buffer.
the respond you get will redirect you to another URL which has the login token.
you need to execute one last HTTP request to basically "validate" that login token, you basically just follow the redirection and you're done.
that token is now ready for use with the client.
then you just launch the client with that token like you normally would:
"game.bin EasyFun -a LOGIN_TOKEN_HERE -p xlwlogin"
Basically, there's no security in this one at all. they use HTTPS but all of the information is just sittin' there in the POST/GET (request AND respond) buffers.
and the login token is literally in the URL buffer in a way that you can even see it in your browser when it's loading.
and it can even be done manually as well, take a look:

that black box is censoring an
actual username and password.
P.S
Not trying to dis the OP in any way, just trying to be informative.
he did an amazing job nonetheless.