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] [day] [month] [year] [list]
Message-ID: <4E2E0482.7030008@genband.com>
Date:	Mon, 25 Jul 2011 18:04:18 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	Pierre Louis Aublin <pierre-louis.aublin@...ia.fr>
CC:	netdev@...r.kernel.org
Subject: Re: tcp/udp checksum on loopback interface

On 07/22/2011 02:01 AM, Pierre Louis Aublin wrote:
> Hello everybody
>
> I am interested in the reliability of TCP and UDP using the loopback
> interface.
> I found that there is no checksum verification on the body of packets
> transmitted through the loopback interface :

> Finally, why this behaviour? Is it because you assume message can not
> get corrupted while staying on the same machine?

That's correct.  We can save cpu time by not doing the checksum because 
we assume that our own hardware won't introduce errors (or if it does 
and we care about them we'll be monitoring the hardware for ECC errors 
anyways).

Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@...band.com
www.genband.com
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ