netdev - IPv6 raw socket and recvfrom

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: <20100817143120.7fad5186@tux.DEF.witbe.net>
Date:	Tue, 17 Aug 2010 14:31:20 +0200
From:	Paul Rolland <rol@...917.net>
To:	netdev@...r.kernel.org
Subject: IPv6 raw socket and recvfrom

Hello,

I'd like someone to clarify the behavior I can expect from a RAW IPv6
socket _in Linux_ :
 - Raw IPv4 sockets : recvfrom() payload contain all the IP header,
   including src ip, dst ip, etc...

 - Raw IPv6 sockets : so far, recvfrom returns me only the payload. I've
   added the HDRINCL options, but it seems that this is a no-op in
   IPv6-land.

I've reviewed RFC 3542, which states that I'm not to expect ip6 header, but
often "there is more than one way to do it", and I'd like to be sure I'm
not missing something obvious

Paul

PS : I'm not subscribed to netdev, so please answer directly...

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