netdev - Re: [PATCH 9/9 v2] net: Add sysctl to trust checksum

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: <CA+mtBx9w6-id5NDuP31yMrhO9Ho8TM2O5oGfneXiT_f+G+Xvag@mail.gmail.com>
Date:	Sun, 27 Apr 2014 21:07:24 -0700
From:	Tom Herbert <therbert@...gle.com>
To:	David Miller <davem@...emloft.net>
Cc:	Stephen Hemminger <stephen@...workplumber.org>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [PATCH 9/9 v2] net: Add sysctl to trust checksum_complete

> If we do anything, we should do it consistently and not just for one
> specific checksum delivery type.
>
> So if we add a sysctl, it should revalidate the checksum in software
> for all checksum offload variants, and such a sysctl should be off by
> default.

Okay, but I would want to add a new checksum type to distinguish
checksum_complete that was done in software as opposed to one received
from a device. I was planning on doing this in a later patch set. I
suppose you can disregard this patch for now.
--
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