[11296] in bugtraq

home help back first fref pref prev next nref lref last post

Re: Linux blind TCP spoofing, act II + others

daemon@ATHENA.MIT.EDU (Alan Cox)
Fri Aug 6 21:46:46 1999

Content-Type: text
Message-Id:  <E11ChB3-0007Hi-00@the-village.bc.nu>
Date:         Fri, 6 Aug 1999 11:24:38 +0100
Reply-To: Alan Cox <alan@LXORGUK.UKUU.ORG.UK>
From: Alan Cox <alan@LXORGUK.UKUU.ORG.UK>
X-To:         solar@FALSE.COM
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  <199908050046.EAA02943@false.com> from "Solar Designer" at Aug 5,
              99 04:46:12 am

> So, the version of my patch for 2.0.34 didn't need to fix this any
> more.  Of course, future updates of the patch I was making based on
> the latest one, and never bothered to check for this bug again.
>
> Now, after your post, I am looking at patch-2.0.35.gz:
>
> -	return 0;
> +	return 1;
>
> So, the "feature" got re-introduced in 2.0.35.  I don't know of the
> reason for this.  I can only guess that the other major TCP changes

It was put back into 2.0.35 because the "fix" caused interoperability
problems with many other stacks.

Alan

home help back first fref pref prev next nref lref last post