netdev - Re: IPV6_RTHDR with a type-0 routing header

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4A8DF3C9.8000808@cn.fujitsu.com>
Date:	Fri, 21 Aug 2009 09:09:29 +0800
From:	Shan Wei <shanwei@...fujitsu.com>
To:	"Steinar H. Gunderson" <sgunderson@...foot.com>
CC:	brian.haley@...com, davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: IPV6_RTHDR with a type-0 routing header

Steinar H. Gunderson wrote, at 08/20/2009 07:11 PM:
> Hi,
> 
> I've tried attaching a type-0 routing header to my IPv6 packets with
> setsockopt(..., IPV6_RTHDR, ...), but the kernel just returns EINVAL.
> looking at the source, it seems it simply refuses anything that's not type-2;
> should that really be right? I found the following commit:
> 
>   http://kerneltrap.org/mailarchive/linux-netdev/2008/11/11/4064594
> 
> However, it only seems to change EPERM into EINVAL. I don't see any

About the cause of changing EPERM into EINVAL, can refer to 
http://marc.info/?l=linux-netdev&m=122046709502496&w=3.

-- 
Best Regards
Shan Wei

> reasonable explanation why it should not be simply success; in fact, RFC 3452
> only seems to talk about using type-0 headers with this option.
> 
> Any ideas?
> 
> /* Steinar */

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