1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
Return-Path: <jlrubin@mit.edu>
Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 596D0C0051
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 24 Aug 2020 20:22:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by whitealder.osuosl.org (Postfix) with ESMTP id 4644B87694
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 24 Aug 2020 20:22:07 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from whitealder.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id CW94cj+hSK1J
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 24 Aug 2020 20:22:06 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by whitealder.osuosl.org (Postfix) with ESMTPS id 6DDC5874E9
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 24 Aug 2020 20:22:06 +0000 (UTC)
Received: from mail-ej1-f41.google.com (mail-ej1-f41.google.com
[209.85.218.41]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07OKM4Yc013698
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Mon, 24 Aug 2020 16:22:05 -0400
Received: by mail-ej1-f41.google.com with SMTP id dp2so8277247ejc.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 24 Aug 2020 13:22:05 -0700 (PDT)
X-Gm-Message-State: AOAM531czm8KisVZerDezZPOd1dutgkbZrYLqka24S72HAx7A8T5vLcf
9+koime+TNzYyDHBzpxFWphAPlI/RTQhkAjhRxo=
X-Google-Smtp-Source: ABdhPJyWgRGTzo3PT2y9KiXxNHMVD0xIAP50Vjec1tkyhJ1wXsHGWUiMbqF6s5+damkd5bV3/cLZw/GuVlD4CRmvJKk=
X-Received: by 2002:a17:906:a3d6:: with SMTP id
ca22mr7116141ejb.78.1598300524018;
Mon, 24 Aug 2020 13:22:04 -0700 (PDT)
MIME-Version: 1.0
References: <CAD5xwhgDWpaavk3R5gjUwMU37bRTmKC+o5hHoWVeaiW8WFQNjA@mail.gmail.com>
<5B76307E-9810-49F1-8289-E0F0E84ACD72@voskuil.org>
In-Reply-To: <5B76307E-9810-49F1-8289-E0F0E84ACD72@voskuil.org>
From: Jeremy <jlrubin@mit.edu>
Date: Mon, 24 Aug 2020 13:21:52 -0700
X-Gmail-Original-Message-ID: <CAD5xwhiSf3isoMsVJiv5KQ3n5ymcS+StigkX_eDe5hmAGra-0Q@mail.gmail.com>
Message-ID: <CAD5xwhiSf3isoMsVJiv5KQ3n5ymcS+StigkX_eDe5hmAGra-0Q@mail.gmail.com>
To: Eric Voskuil <eric@voskuil.org>
Content-Type: multipart/alternative; boundary="000000000000fa800c05ada55656"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Generalizing feature negotiation when new p2p
connections are setup
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2020 20:22:07 -0000
--000000000000fa800c05ada55656
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Mon, Aug 24, 2020 at 1:17 PM Eric Voskuil <eric@voskuil.org> wrote:
> I said security, not privacy. You are in fact exposing the feature to any
> node that wants to negotiate for it. if you don=E2=80=99t want to expose =
the buggy
> feature, then disable it. Otherwise you cannot prevent peers from accessi=
ng
> it. Presumably peers prefer the new feature if they support it, so there =
is
> no need for this complexity.
>
>
>
I interpreted* " This seems to imply a security benefit (I can=E2=80=99t di=
scern
any other rationale for this complexity). It should be clear that this is
no more than trivially weak obfuscation and not worth complicating the
protocol to achieve.", *to be about obfuscation and therefore privacy.
The functionality that I'm mentioning might not be buggy, it might just not
support peers who don't support another feature. You can always disconnect
a peer who sends a message that you didn't handshake on (or maybe we should
elbow bump given the times).
--000000000000fa800c05ada55656
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Mon, Aug 24, 2020 at 1:17 PM Eric Voskuil <<a href=3D"mail=
to:eric@voskuil.org">eric@voskuil.org</a>> wrote:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div dir=3D"ltr">I s=
aid security, not privacy. You are in fact exposing the feature to any node=
that wants to negotiate for it. if you don=E2=80=99t want to expose the bu=
ggy feature, then disable it. Otherwise you cannot prevent peers from acces=
sing it. Presumably peers prefer the new feature if they support it, so the=
re is no need for this complexity.</div><div dir=3D"ltr"><br></div><br></di=
v></blockquote><div><br></div><div style=3D"font-family:arial,helvetica,san=
s-serif;font-size:small;color:rgb(0,0,0)" class=3D"gmail_default">I interpr=
eted<b> "<span class=3D"gmail-im">
This seems to imply a security benefit (I can=E2=80=99t discern any other=
=20
rationale for this complexity). It should be clear that this is no more=20
than trivially weak obfuscation and not worth complicating the protocol=20
to achieve.</span>", </b>to be about obfuscation and therefore privacy=
.</div><div style=3D"font-family:arial,helvetica,sans-serif;font-size:small=
;color:rgb(0,0,0)" class=3D"gmail_default"><br></div><div style=3D"font-fam=
ily:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)" class=3D"g=
mail_default">The functionality that I'm mentioning might not be buggy,=
it might just not support peers who don't support another feature. You=
can always disconnect a peer who sends a message that you didn't hands=
hake on (or maybe we should elbow bump given the times).<br></div><div styl=
e=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0=
)" class=3D"gmail_default"><b></b></div></div></div>
--000000000000fa800c05ada55656--
|
