Re: Address privacy

Fernando Gont <fgont@si6networks.com> Tue, 28 January 2020 23:45 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0D08120104 for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 15:45:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cVlxVAq5Pfho for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 15:45:26 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC46120020 for <ipv6@ietf.org>; Tue, 28 Jan 2020 15:45:25 -0800 (PST)
Received: from [192.168.100.103] (unknown [186.183.48.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 9BC1A86B47; Wed, 29 Jan 2020 00:45:22 +0100 (CET)
Subject: Re: Address privacy
To: Tom Herbert <tom@herbertland.com>
Cc: Nick Hilliard <nick@foobar.org>, 6man WG <ipv6@ietf.org>
References: <03C832CE-7282-4320-BF1B-4CB7167FE6BE@employees.org> <1962.1579823388@localhost> <f83ab037-9125-bb74-dbac-68850aeb1020@huitema.net> <CBB23ABE-A7A3-4208-873C-E47EE063E34B@fugue.com> <11855.1579980079@localhost> <CALx6S36V_VjaxhELYcsgDYLWsCkj20p6gtiY9T9Q=9-9Oibyjw@mail.gmail.com> <32626.1580060558@localhost> <CALx6S37prWACD0jv9c-XHD-JtPqZAcgeT2Ax0EZHkiQaDR4t=g@mail.gmail.com> <419b7c7a-e364-7951-5a44-6c39e1da65fb@joelhalpern.com> <CALx6S36802oDaEgojAPq2c6hM_s1BayidXPh1Sc6RZmZa9UHpQ@mail.gmail.com> <6c5ba72d-9289-90ba-a1c9-2307ed29a4da@foobar.org> <a98bf2ab-32e7-459b-14d2-5e0e1c65a229@si6networks.com> <CALx6S36J5TPnXJQyMW2NUbQV6KL_oqUQ01m+BEzBJ+xcHpmQWw@mail.gmail.com> <bc0d1eb8-2301-224d-dc33-19f6a60e593e@si6networks.com> <CALx6S34i67ivt8t1P3omRVzsj9NfxY2t41JLjmjT6X0vtBQHKQ@mail.gmail.com> <1fc7816e-6179-28d6-7b11-be2027561a54@si6networks.com> <CALx6S37KXfLE22uHMZTD41+jR7fdZd9PZGqO-r4SE2LehtN=Gg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <2d312ecf-e037-5c24-28d7-2a2c3dc06363@si6networks.com>
Date: Tue, 28 Jan 2020 20:02:31 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CALx6S37KXfLE22uHMZTD41+jR7fdZd9PZGqO-r4SE2LehtN=Gg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pM8opSAsJsaJwckWV53o1PCmDag>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2020 23:45:29 -0000

On 28/1/20 19:45, Tom Herbert wrote:
[...]
>> I don't think you can quantify privacy. What would be the units for that?
>>
>> There's secrecy and not-secrecy. But with these things, you simply
>> mitigate (to some extent) the ability to correlate network activity.
>>
> Fernando,
> 
> In the case of single use addresses, that is each flow gets its own
> addresses, the privacy effects are quantifiable. Since each flow has a
> different source address, no two flows or communications can be
> correlated to being sourced from the same user. In this case, the
> identifiers are not reused is used in multiple contexts, so it isn't
> possible to correlate seemingly unrelated activity using an
> identifier. When an identifier is reused for the same node, even once,
> then the possibility of correlations exists.

You are not quantifying privacy: that's still qualitative description.




>>> One might compare this to the policy of some sys admins that users need
>>> to change passwords regularly. The rationale is similar, but that
>>> practice has been most debunked as not improving security and in fact is
>>> more of a burden to users that providing any real value.
>>
>> I don't think it has been debunked. Certainly, if you change your
>> password, you limit the ability of the attacker that had obtained your
>> password from re-using the same credentials. (assuming they are not used
>> for a system where they can install backdoors, etc.). Most things we
>> emply for security have an associated lifetime...
>>
> It's a false sense of security. Here's a good analysis:
> https://www.ftc.gov/news-events/blogs/techftc/2016/03/time-rethink-mandatory-password-changes

Forcing password changes exacerbate some human aspects, and at times 
leads to trouble. That doesn't say it doesn't have a place.

Folks also argue that firewalls are a false sense of security. Some 
argue the same about resistance to address-scan -- even when the #1 task 
to hack a system is normally to find it. IMO, whatever makes the 
attacker's life harder has a place and a use.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492