At 04:20 AM 4/25/00 -0500, Taral wrote:
> > Look at your sample in code, it is invalid. It cannot be generated by
> > some real TCP stack.
>
>I see. Yes, the remote TCP stack is probably broken. Very well, I will
>keep it as a local patch available to those who want it. You may remove
>the code, as it is not required by standards-conformant TCP stacks.
I'd watch out for that statement. The RFCs are clear that a TCP/IP stack
conforming to the standards defined there should be able to handle anything
thrown at it: properly formed, malformed, pathologically formed, or even
completely random data. In my opinion, if the code you are talking about
takes care of forms 2 through 4 above, then it should stay in.
Satch
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
