search

Google-Code-Fork / tibiaapi

Automatically exported from code.google.com/p/tibiaapi
MIT License
0 stars 0 forks source link

Logging In #89

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Login using the proxy.
2. Close your program forcing your players connection to be closed.
3. Restart your program and login.

What is the expected output? What do you see instead?
You should be able to log back in, but it sits on the character list
loading screen.

I have to close my program, close the Tibia client, and restart everything
to log in.

Original issue reported on code.google.com by joebingham07@gmail.com on 19 Dec 2008 at 7:00

GoogleCodeExporter commented 9 years ago 
It also seems to happen when I load the Tibia client using the client chooser, 
close
my program without logging in, then start my program and try to login.

Original comment by joebingham07@gmail.com on 19 Dec 2008 at 7:03

GoogleCodeExporter commented 9 years ago 
If you stop the program by killing it or by pressing "Stop Debugging" in visual
studio the method ~Proxy() will not be called, maybe this is the problem, but I 
will
do some tests here.

Original comment by brunodun...@gmail.com on 19 Dec 2008 at 5:08

GoogleCodeExporter commented 9 years ago 
i guess since the destructor isn't called, the RSA key will still be the one 
used for
OTs, so when you restart the program it will think you are trying to connect to 
a OT
and won't reencrypt the packet with cip's key(at ParseFirstClientMsg()).
Maybe a fix for that would be not changing the key at all and getting the 
client's
version internally using the client.Version property and the xtea key by 
reading the
memory.

Original comment by geancarl...@gmail.com on 25 Mar 2009 at 8:27

GoogleCodeExporter commented 9 years ago 
Is that how the proxy tells if you are using an OT server or not? Why not 
instead
check the login server IP you are connecting to, and if it is in the known list 
for
CIP use the official RSA, if not, use the OT one. Then when you restart your 
program
and use the same client, it will be the address you connect to that determines 
how
the login packet is encrypted.

Original comment by ian320 on 25 Mar 2009 at 9:23

GoogleCodeExporter commented 9 years ago 
That wouldn't work quite well because we would have localhost as login servers 
after
using the proxy. i think my solution for this issue is satisfying since it's 
not a
big deal to "ask" the user what he is connecting to.

Original comment by geancarl...@gmail.com on 21 Jul 2009 at 6:58

GoogleCodeExporter commented 9 years ago

Original comment by geancarl...@gmail.com on 21 Jul 2009 at 6:58