Re: Disabling temporary addresses by default?

[Lorenzo Colitti <[e-mail]>]

On Wed, Jan 29, 2020 at 2:46 AM Gyan Mishra <[e-mail]> wrote:

>    The main reason this topic comes has up is due to possible impact of
> usage of the temporary address when it gets deprecated with long lived
> session.  That’s the crux of why this topic is critical and has severe
> operational impact. When the address changes for long lived connections
> from the deprecated temporary address to the new preferred address, the
> session would terminate and have to re-establish, which is impacts the user.
>

If there is a permanent address as well, then an application that is not
able to deal with session resets (like SSH) can use
the IPV6_PREFER_SRC_PUBLIC socket options to use the permanent address
instead.


> This would allow us to maintain privacy extension temporary address
> enabled by default change to benefit privacy advocates and also eliminate
> impact for enterprise users where availability and stability is utmost
> importance.
>

But don't enterprises care about not leaking the habits of their employees?
If I was on an enterprise security team, I would be pretty concerned about
the levels of leakage and cross-site tracking that are enabled by never
changing the IPv6 addresses of a host. This doesn't happen in IPv4 because
we use NAT, but it will definitely happen in IPv6.