netdev - Re: [PATCH] ipv4/ipv6: check hop limit field on input

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: <4A240681.2010300@6wind.com>
Date:	Mon, 01 Jun 2009 18:49:05 +0200
From:	Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:	Florian Westphal <fw@...len.de>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH] ipv4/ipv6: check hop limit field on input

Le 01.06.2009 18:19, Florian Westphal a écrit :
> Nicolas Dichtel <nicolas.dichtel@....6wind.com> wrote:
>> when network stack receives a packet, it didn't check value of ttl/hop 
>> limit
>> field. RFC indicates that a router must drop the packet if this field is 0.
> 
> Whats wrong with the checks in ip(6)_forward?
It's on forward, not on input. Router must not process it.
For example, if you try to ping (with ttl set to 0) the router, you will receive 
a reply.

Nicolas
--
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