netdev - Re: PROBLEM: raw sockets rewriting IP ID in rare cases.

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100814.223532.242143460.davem@davemloft.net>
Date:	Sat, 14 Aug 2010 22:35:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	morgon.j.kanter@...tmouth.edu
Cc:	netdev@...r.kernel.org
Subject: Re: PROBLEM: raw sockets rewriting IP ID in rare cases.

From: "Morgon J. Kanter" <morgon.j.kanter@...tmouth.edu>
Date: Fri, 13 Aug 2010 13:07:38 -0400

> I have stumbled across what I think is a rare bug in the raw socket mechanism 
> of the kernel. When attempting to send a certain packet with an IP ID of zero 
> from a raw socket created with the call "socket(AF_INET, SOCK_RAW, 
> IPPROTO_RAW)", the kernel will modify the IP ID field and update the checksum. 
> It only seems to do it with this specific packet for some reason, similar 
> packets with an IP ID of zero do not get so mangled.

Even when using hdrinclude mode of RAW ipv4 sockets, if you specify
a zero ID field, the kernel will fill it in with the usual value.

It is expected behavior.

If you want the kernel to leave your ID field alone, provide a
non-zero one.
--
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