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]
Message-Id: <200803122006.49506.rdenis@simphalempin.com>
Date:	Wed, 12 Mar 2008 20:06:48 +0200
From:	Rémi Denis-Courmont <rdenis@...phalempin.com>
To:	Octavian Purdila <opurdila@...acom.com>
Cc:	netdev@...r.kernel.org
Subject: Re: question regarding (AF_INET6, SOCK_RAW, IPPROTO_RAW) sockets

Le Wednesday 12 March 2008 18:34:29 Octavian Purdila, vous avez écrit :
> Hi,
>
> I've noticed that when using IPv6 raw sockets with IPPROTO_RAW protocol and
> IPV6_PKTINFO set, we are not allow to specify a source address that it is
> not configured in the system.
>
> Disabling ipv6_chk_addr in datagram_send_ctl for IPv6 raw sockets seems to
> fix our problem. Is this approach the right one?

I am a bit confused here. Why would you use IPV6_PKTINFO with a network-layer 
raw socket? You have to write the IPv6 header anyway, so what useful 
additional infos would you the ancillary data contain?

-- 
Rémi Denis-Courmont
--
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