netdev - Re: [PATCH] RAW6: Do not allow set IPV6

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: <20080420.003328.45324753.davem@davemloft.net>
Date:	Sun, 20 Apr 2008 00:33:28 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	wangchen@...fujitsu.com
Cc:	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org
Subject: Re: [PATCH] RAW6: Do not allow set IPV6_CHECKSUM for ICMPv6 socket

From: Wang Chen <wangchen@...fujitsu.com>
Date: Sun, 20 Apr 2008 15:18:52 +0800

> Why not remove the RFC-breaking code from applications?

Because once applications exist and are deployed we cannot break them
with careless kernel changes.  A user should not get a broken
traceroute6 binary just because he upgrades his kernel, that's
a bug.

The RFC is not a set of laws that must be followed under all
circumstances.  In this case it is worse to break applications on
people's systems than be compliant to some standard.

You need to understand this basic premise before we can communicate at
all about this topic.
--
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