netdev - Re: [patch iproute2 v2 0/2] add support for IFA_F

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:	Sat, 4 Jan 2014 12:15:46 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Jiri Pirko <jiri@...nulli.us>
Cc:	netdev@...r.kernel.org, stephen@...workplumber.org,
	thaller@...hat.com
Subject: Re: [patch iproute2 v2 0/2] add support for IFA_F_MANAGETEMPADDR

On Sat, Jan 04, 2014 at 12:05:57PM +0100, Jiri Pirko wrote:
> Sure. NM should set use_tempaddr accordingly. You are right that kernel
> generate temporary adresses, but only for the prefixes received via
> neighbor discovery (see addrconf_prefix_rcv). The ones that are set by
> hand are not handled. That is the reason we introduced IFA_F_MANAGETEMPADDR.

Ah, sorry. So NM sets use_tempaddr == 2 but disables accept_ra? That's fine,
sorry to bother!

> >So currently privacy addresses are correctly installed, but we cannot control
> >if we want prefer them to global addresses for outgoing connections where the
> >socket is not bound to a specific address.
> >
> >Also, I saw that NetworkManager switched to install autoconf addresses
> >as /128, doesn't this break with IFA_F_MANAGETEMPADDR, as you expect a /64
> >prefixlen?
> 
> /64 is required

Ok, currently NM seems to "violate" that as it installs autoconf addresses
with 128 prefixlen, so IFA_F_MANAGETEMPADDR should not work on them.
(currently observed on Fedora 20).

Greetings,

  Hannes

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