[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MiNTNET Bug spotted.



> Active TCP connections
> Proto  Recv-Q Send-Q Local-Address        Foreign-Address      State
> TCP         0   1156 203.4.148.180:http   134.173.42.2:-12063  CLOSING        
> TCP         0      0 203.4.148.180:1023   203.4.148.1:login    ESTABLISHED    
> TCP        67      0 203.4.148.180:1024   203.4.148.1:6250     ESTABLISHED    
> 
> See the http request? This data will never arrive. I assume it's because
> the port number should be being handled as unsigned, but is getting
> treated as signed, instead.
> 
> I've given this extensive testing over the last hour. Linux's http server
> doesn't have a problem with the requesting site, but my box does. But
> _ONLY_ when the port number appears to be negative.

Hmm, the only things that are done with portnumbers is to compare them with
others (ie. test for equality). Should make no harm if they are greater than
0x7fff (ie. negative in 16 bits).

Perhaps the -12063 isn't the port number of the other side (but instead some
ramdom number inserted as the port number due to a bug)? Can you perhaps check
the port number on the remote host if you have an account there?

Kay.
--
Kay Roemer              roemer@informatik.uni-frankfurt.de
"If I ever meet ..."    http://www.uni-frankfurt.de/~roemer/
"... myself I'll hit myself so hard I won't know who hit me" (Zaphod)