Bug#762698: jumpnbump: server refuses network connections

[Julian Marchant]

Package: jumpnbump
Version: 1.51+dfsg1-1

When a Jump'n'Bump client attempts to connect to a Jump'n'Bump server,
the server refuses the connection on the basis of a bogus invalid player
number. I'll let the example speak for itself. Here is the output from
the server:

$ jumpnbump -server 1 -player 0
Opened audio at 44100Hz 16bit stereo, 2048 bytes audio buffer
SERVER: we are (null) (0.0.0.0:26411).
SERVER: waiting for (1) clients...
SERVER: Got data from localhost (127.0.0.1:14260).
SERVER: Client claims to be player #140256452018177.
SERVER:  (that's an invalid player number.)
SERVER: Forbidding connection.

And here is the output from the client, on the same system:

$ jumpnbump -connect localhost -player 1
Opened audio at 44100Hz 16bit stereo, 2048 bytes audio buffer
CLIENT: we are (null) (0.0.0.0:26411).
CLIENT: connected to localhost...
CLIENT: Sending HELLO packet...
CLIENT: Waiting for ACK from server...
CLIENT: Server forbid us from playing.

What you might notice is that even though the client has a player number
specified as 1, the server thinks the number is 140256452018177. The
number seems to be completely random between runs, but consistent within
one run; in that same run, if I specified -player 2 from the client, the
server would think the number to be 140256452018178.

I should also note that the number specified by the client seems to be
an unsigned 32-bit integer (-1 is equivalent to 4294967295), so there's
no possible workaround.