netdev - Re: XFRM and IPv6 raw sockets and multicast

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]

Date:	Tue, 04 Dec 2007 07:52:01 -0800 (PST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	hugosantos@...il.com
Cc:	netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org
Subject: Re: XFRM and IPv6 raw sockets and multicast

Hello.

In article <9c46321e0712040727tee578cm97a83936fefb34ed@...l.gmail.com> (at Tue, 4 Dec 2007 16:27:50 +0100), "Hugo Santos" <hugosantos@...il.com> says:

>   The behavior is the same as in UDP, but ipv6_pinfo->saddr is not
> usually set for these kind of sockets. I would say that if fl6_src is
> any, it should be copied from the ipv6 header.

What do you mean by "ipv6 header"?

>   Another question is why does raw.c require a msg_name? If
> inet->hdrincl was set, it could use the ipv6 header destination
> address in the absense of msg_name.

I think hdrincl is broken (and even, say, deprecated) on IPv6.

If we do really support it, if hdcincl is set, XFRM and other
all extension header processes should be skipped, but they are
not very clear at all so far.

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