Bug 53762 - playerid desynchronisated after reconnect
Summary: playerid desynchronisated after reconnect
Status: RESOLVED FIXED
Alias: None
Product: atlantik
Classification: Applications
Component: monopd (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Rob Kaper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-31 19:26 UTC by Sylvain Rochet
Modified: 2003-10-17 16:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sylvain Rochet 2003-01-31 19:26:55 UTC 
Version:           0.8.0 CVS 2003/01/31 (using KDE KDE 3.1)
Installed from:    Debian stable Packages
OS:          Linux

If reconnect lot of time that exceed maximum number of
reconnections... monopd get in real trouble when creating
a new game:

-- for example:

server send playerid = 125
and a possible list of player is:
126
128
132

Strange !

I consider that has a security hole... it's impossible to create
a game after that :(

Sylvain Rochet
Comment 1 Rob Kaper 2003-02-02 18:44:02 UTC 
When was the player disconnected (Config, Run, etc) ? What XML do you get after 
the reconnection? Why would you need to reconnect more than once?
Comment 2 Rob Kaper 2003-06-19 07:06:31 UTC 
Oh, and what's "the maximum number of reconnections?" .. do you mean you're 
hitting the server limits by keeping tons of connections open?
Comment 3 Sylvain Rochet 2003-06-23 14:53:17 UTC 
the bug is still here, I've reproduced this one sometime, but dummo how
reproduce this one :(
Comment 4 Rob Kaper 2003-10-17 16:27:32 UTC 
Socket connections no longer automatically create a new player, so this should no longer be a problem. Furthermore, sockets timeout if an appropriate handshake is not sent in time.

Monopd CVS >= 20031017 (to be 0.9.0), requires libcapsinetwork CVS.. (to be 0.2.4).