netdev - Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want to know why its set to zero)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87r69ssd4q.fsf@basil.nowhere.org>
Date:	Thu, 17 Jul 2008 18:12:53 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	netdev@...r.kernel.org
Subject: Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want to know why its set to zero)

Christoph Lameter <cl@...ux-foundation.org> writes:

> There is some security reason why we set IP_ID == 0 right? Could someone point me at the discussions that lead to having IP_ID be zero? Have not been involved in network that much so forgive my ignorance.... and I can only find some hints about why this was done here and there using google.

AFAIK it was just for efficiency. The way Linux generates ipids
currently is somewhat expensive, because it aims to generate a per ip
ipid counter, so it was turned off when not needed. I used to patch
that out because it always seemed like overkill to me.

-Andi
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html