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: <4E2AF71A.6080703@inria.fr>
Date:	Sat, 23 Jul 2011 18:30:18 +0200
From:	Pierre Louis Aublin <pierre-louis.aublin@...ia.fr>
To:	netdev@...r.kernel.org
Subject: loopback interface - why checksum on header?

Hello everybody

I am wondering why the checksum of packets sent through the loopback 
interface is computed on the header only.
If I understand correctly, it is assumed that a message cannot be 
corrupted in RAM, thus there is no need to verify the integrity of the 
whole message.
However, in that case, there is also no need to compute it on the header.
Consequently, why is it not the case?

Thank you in advance
Pierre Louis Aublin
--
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