linux-kernel - Sending UDP packets to port 0

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

Message-ID: <485E0B1C.7030105@digadd.de>
Date:	Sun, 22 Jun 2008 11:19:40 +0300
From:	"Christian P. Schmidt" <schmidt@...add.de>
To:	linux-kernel@...r.kernel.org
Subject: Sending UDP packets to port 0

Hi all,

I know that the kernel forbids sending UDP packets to port 0. Is there a 
specific reason for this?

I'm asking because I regularly need to access a device that asks for 
tftp files using port 0 as source. To use these devices I'm using a 
kernel with removed port 0 checks.

I read RFC 768, and it does not explicitly forbid the use of port 0 as 
far as I can see. It only says that if unused, 0 is to be inserted.

RFC 1350 (TFTP) even states explicitly:
The transfer identifiers (TID's) used by TFTP are passed to the Datagram 
layer to be used as ports; therefore they must be between 0 and 65,535.

In my understanding, and apparently that of the authors of the 
appliance's tftp client implementation, this marks port 0 as valid.

Please CC: me on any replies as I am not subscribed to the list.

Regards,
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/