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
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <eric@voskuil.org>) id 1YJUFg-0007nI-8c
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 21:46:20 +0000
X-ACL-Warn:
Received: from mail-pd0-f181.google.com ([209.85.192.181])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YJUFf-0005np-7j
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 21:46:20 +0000
Received: by pdbnh10 with SMTP id nh10so7640308pdb.12
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Feb 2015 13:46:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:references:mime-version:in-reply-to:content-type
:content-transfer-encoding:message-id:cc:from:subject:date:to;
bh=LoDLP9ClVcO1tU6xGDfS5tga8CBNu/ixAuYgkMs2QLU=;
b=WIZxMfgvTTsBJFmWfNGGNVU47wFOLNE7dL9RuDO0PfR40yZ7athEdosZI6Rey65z0H
Bo2cBz565Ad5rH/JYBJl3JRHJcpoZFRbDOqB2D88WvyDftFOGcmbyk+4N9Z7UEOYXjYq
WVj4xjxlLuSHG3MgywSBrV0HXbsZd/ujejieDZBsspkzVRMDgDqg0NEhFQw3nmvVXg4j
7IKW/EtjJqayZVzrJzt3OOOiJll74ovT42RrA0+jyURS0FVVTOUJrPJJWgel/N8KM1fE
gIw2zJQjtFZ8+4OQWMxisUbdljKIg8uUlE/SH5voTqWAvsUPrpC/ywCwrlEV6nNkFG7j
g/NA==
X-Gm-Message-State: ALoCoQmj8Vb8wxK7N332U0lnfHfwxio5o0o0F9gQnXQKWKWyk4skSGdms/gzXBQneGn/Lfnra2N+
X-Received: by 10.68.69.110 with SMTP id d14mr378646pbu.77.1423172773466;
Thu, 05 Feb 2015 13:46:13 -0800 (PST)
Received: from [10.195.38.15] ([166.170.37.215])
by mx.google.com with ESMTPSA id fg6sm6006887pdb.24.2015.02.05.13.46.12
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 05 Feb 2015 13:46:12 -0800 (PST)
References: <CABdy8DKS4arkkCLGC=66SUJm5Ugib1EWP7B6MkQRX1k-yd3WBw@mail.gmail.com>
<CANEZrP3v=ySS4gragaWuBMWi_swocRRRq_kw2edo6+9kifgrFQ@mail.gmail.com>
<54D3D636.1030308@voskuil.org>
<CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
<279489A5-1E46-48A2-8F58-1A25821D4D96@gmail.com>
<CANEZrP3VAWajxE=mNxb6sLSQbhaQHD=2TgRKvYrEax2PAzCi2A@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CANEZrP3VAWajxE=mNxb6sLSQbhaQHD=2TgRKvYrEax2PAzCi2A@mail.gmail.com>
Content-Type: multipart/alternative;
boundary=Apple-Mail-F4DA88C2-53D8-40A7-920E-2B468C2479F9
Content-Transfer-Encoding: 7bit
Message-Id: <6AEDF3C4-DEE0-4E31-83D0-4FD92B125452@voskuil.org>
X-Mailer: iPhone Mail (12B440)
From: Eric Voskuil <eric@voskuil.org>
Date: Thu, 5 Feb 2015 13:46:10 -0800
To: Mike Hearn <mike@plan99.net>
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
X-Headers-End: 1YJUFf-0005np-7j
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Paul Puey <paul@airbitz.co>
Subject: Re: [Bitcoin-development] Proposal for P2P Wireless (Bluetooth LE)
transfer of Payment URI
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 21:46:20 -0000
--Apple-Mail-F4DA88C2-53D8-40A7-920E-2B468C2479F9
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
BLE has an advertised range of over 100m.=20
http://www.bluetooth.com/Pages/low-energy-tech-info.aspx
In the case of mass surveillance that range could most likely be extended dr=
amatically by the reviewer. I've seen WiFi ranges of over a mile with a str=
ong (not FCC approved) receiver.
WiFi hotspots don't have strong identity or a guaranteed position, so they c=
an't be trusted for location.
e
On Feb 5, 2015, at 1:36 PM, Mike Hearn <mike@plan99.net> wrote:
>> This sounds horrible. You could basically monitor anyone with a wallet in=
a highly populated area and track them super easily by doing facial recogni=
tion.
>=20
> We're talking about BLE, still? The radio tech that runs in the so called "=
junk bands" because propagation is so poor?
>=20
> My watch loses its connection to my phone if I just put it down and walk a=
round my apartment. I'm all for reasonable paranoia, but Bluetooth isn't goi=
ng to be enabling mass surveillance any time soon. It barely goes through ai=
r, let alone walls.
>=20
> Anyway, whatever. I'm just bouncing around ideas for faster user interface=
s. You could always switch it off or set it to be triggered by the presence o=
f particular wifi hotspots, if you don't mind an initial bit of setup.
>=20
> Back on topic - the debate is interesting, but I think to get this to the s=
tage of being a BIP we'd need at least another wallet to implement it? Then I=
guess a BIP would be useful regardless of the design issues. The prefix mat=
ching still feels flaky to me but it's hard to know if you could really swip=
e payments out of the air in practice, without actually trying it.
>=20
>=20
--Apple-Mail-F4DA88C2-53D8-40A7-920E-2B468C2479F9
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>BLE has an advertised range of over 10=
0m. </div><div><br></div><div><a href=3D"http://www.bluetooth.com/Pages=
/low-energy-tech-info.aspx">http://www.bluetooth.com/Pages/low-energy-tech-i=
nfo.aspx</a><br><br><span style=3D"background-color: rgba(255, 255, 255, 0);=
">In the case of mass surveillance that range could most likely be extended d=
ramatically by the reviewer. I've seen WiFi ranges of over a mile with=
a strong (not FCC approved) receiver.</span></div><div><span style=3D"backg=
round-color: rgba(255, 255, 255, 0);"><br></span></div><div>WiFi hotspots do=
n't have strong identity or a guaranteed position, so they can't be trusted f=
or location.</div><div><span style=3D"background-color: rgba(255, 255, 255, 0=
);"><br></span></div><div><span style=3D"background-color: rgba(255, 255, 25=
5, 0);">e</span></div><div><br>On Feb 5, 2015, at 1:36 PM, Mike Hearn <<a=
href=3D"mailto:mike@plan99.net">mike@plan99.net</a>> wrote:<br><br></div=
><blockquote type=3D"cite"><div><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><=
div>This sounds horrible. You could basically monitor anyone with a wallet i=
n a highly populated area and track them super easily by doing facial recogn=
ition.</div></div></blockquote><div><br></div><div>We're talking about BLE, s=
till? The radio tech that runs in the so called "junk bands" because propaga=
tion is so poor?</div><div><br></div><div>My watch loses its connection to m=
y phone if I just put it down and walk around my apartment. I'm all for reas=
onable paranoia, but Bluetooth isn't going to be enabling mass surveillance a=
ny time soon. It barely goes through air, let alone walls.</div><div><br></d=
iv><div>Anyway, whatever. I'm just bouncing around ideas for faster user int=
erfaces. You could always switch it off or set it to be triggered by the pre=
sence of particular wifi hotspots, if you don't mind an initial bit of setup=
.</div><div><br></div><div>Back on topic - the debate is interesting, but I t=
hink to get this to the stage of being a BIP we'd need at least another wall=
et to implement it? Then I guess a BIP would be useful regardless of the des=
ign issues. The prefix matching still feels flaky to me but it's hard to kno=
w if you could really swipe payments out of the air in practice, without act=
ually trying it.</div><div><br></div><div><br></div></div></div></div>
</div></blockquote></body></html>=
--Apple-Mail-F4DA88C2-53D8-40A7-920E-2B468C2479F9--
|
