From owner-freebsd-net@FreeBSD.ORG Wed Apr 30 16:05:44 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30D6437B401 for ; Wed, 30 Apr 2003 16:05:44 -0700 (PDT) Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9144F43F75 for ; Wed, 30 Apr 2003 16:05:41 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: from blossom.cjclark.org (12-234-159-107.client.attbi.com[12.234.159.107]) by rwcrmhc53.attbi.com (rwcrmhc53) with ESMTP id <2003043023054105300f824ve>; Wed, 30 Apr 2003 23:05:41 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.8p1/8.12.3) with ESMTP id h3UN5eki004444; Wed, 30 Apr 2003 16:05:40 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.8p1/8.12.8/Submit) id h3UN5dHP004443; Wed, 30 Apr 2003 16:05:39 -0700 (PDT) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to crist.clark@attbi.com using -f Date: Wed, 30 Apr 2003 16:05:39 -0700 From: "Crist J. Clark" To: "."@babolo.ru Message-ID: <20030430230539.GB3912@blossom.cjclark.org> References: <200304302142.h3ULgZ0i056433@khavrinen.lcs.mit.edu> <1051741424.259802.1572.nullmailer@cicuta.babolo.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1051741424.259802.1572.nullmailer@cicuta.babolo.ru> User-Agent: Mutt/1.4.1i X-URL: http://people.freebsd.org/~cjc/ cc: Garrett Wollman cc: net@FreeBSD.org Subject: Re: Reducing ip_id information leakage X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Crist J. Clark" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 23:05:44 -0000 On Thu, May 01, 2003 at 02:23:44AM +0400, "."@babolo.ru wrote: > > < said: [snip] > > The trouble is that we need sequences that are guaranteed not to > > repeat too fast -- and even then we'll still break on modern networks > > anyway, as I noted in my comment. > Why not to use 16 bit of 32 bit pseudorandom generator? Uhh... I might be missing a joke here, but the problem is that after you put 65536 packets onto the wire, the next one _must_ have a repeated IP ID (since there are only 65536 possible). Choosing a random IP ID only can make this problem worse. As many of the references perviously discussed or a very simple calculation on your own will show, with a perfect random generator, after about 300 packets, there is a 50-50 chance the next packet's IP ID will collide (good ol' "birthday paradox"). -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org