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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <eric@voskuil.org>) id 1YJUYW-0001cq-Dj
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 22:05:48 +0000
X-ACL-Warn:
Received: from mail-pd0-f180.google.com ([209.85.192.180])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YJUYV-0006Oc-E2
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 22:05:48 +0000
Received: by pdbfp1 with SMTP id fp1so10320617pdb.4
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Feb 2015 14:05:41 -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=a51MKyv0jsYKc2VO9Rt9i1WLu5UJJBDujb+nZeRg1xo=;
b=REIPlJwyYiBAVIg4qUMKPhXQOUegTZfkN0+nhQzxWSoqNXUEd9EW/+eQ2H18COZNVN
M7Ptx6Q2MABFaHwW81DP7vRgpYIRij8c6WNlhUuxJ8xG5oADYYohMsUQUzOVIG/JKd9X
lHzFMQQSHOvTfeXIbJzxRHT2m/y2m3Xla7mKgifjYnVn2VtEGPSMdTndBYBfJjY5RqeS
iRKQD23rtbWsrE8ROrRiTyZ5tVcVgV+AXGtsDNNPJ9R6xIyE+BEiBVkeaBMwGpxADe6v
HZIQTi/FjyOX9OyluIWZA1W0q2xhtfnvZ7fSigI68ECEoREfDkZEuRJ1VDR3m1GABcdZ
nORg==
X-Gm-Message-State: ALoCoQkvMvoAogp++UsaaWMVBJveuINrFfUh/lCu1L+PnwVp04Lf3fsX4XHE3haur5hk7Ah+/g46
X-Received: by 10.66.186.110 with SMTP id fj14mr511903pac.98.1423173941710;
Thu, 05 Feb 2015 14:05:41 -0800 (PST)
Received: from [10.195.38.15] ([166.170.37.215])
by mx.google.com with ESMTPSA id go1sm5303433pbd.75.2015.02.05.14.05.40
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 05 Feb 2015 14:05:41 -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>
<CABdy8DKdJt+KpU5eaPyB_p6PX3wet2ZgWa-X0gHgPhNXC+HYiw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CABdy8DKdJt+KpU5eaPyB_p6PX3wet2ZgWa-X0gHgPhNXC+HYiw@mail.gmail.com>
Content-Type: multipart/alternative;
boundary=Apple-Mail-471BA261-CD5F-480F-89A2-32F8B652507C
Content-Transfer-Encoding: 7bit
Message-Id: <87E6D928-B615-4A8D-8BBB-3610DB1C08A2@voskuil.org>
X-Mailer: iPhone Mail (12B440)
From: Eric Voskuil <eric@voskuil.org>
Date: Thu, 5 Feb 2015 14:05:39 -0800
To: Paul Puey <paul@airbitz.co>
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 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YJUYV-0006Oc-E2
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 22:05:48 -0000
--Apple-Mail-471BA261-CD5F-480F-89A2-32F8B652507C
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Hi Paul,
The issue is in the establishment of trust. Anyone can broadcast the initial=
information.
e
> On Feb 5, 2015, at 2:01 PM, Paul Puey <paul@airbitz.co> wrote:
>=20
> The broadcast is ONLY done when the wallet is in Receive mode. Same as whe=
n the QR code is visible. The use of the *Name* section is specifically so t=
hat a recipient can broadcast their name/handle. Not so the recipient would b=
roadcast the name of the Sender.
>=20
> On Thu, Feb 5, 2015 at 12:50 PM, Mike Hearn <mike@plan99.net> wrote:
>>> I'm imagining myself walking around broadcasting my photo and MAC
>>> address while hucksters push payment requests to me for approval
>>=20
>> I hate to break it to you, but you broadcast a photo of your face every t=
ime you walk outside ;)
>>=20
>> Bluetooth MAC addresses are random, they aren't useful identifiers. If so=
meone can see you, a face is a far more uniquely identifying thing than a MA=
C.
>>=20
>> "Payment spam" might be a problem. I can imagine a wallet requiring that s=
uch requests are signed and then spammers can be blacklisted in the usual fa=
shion so they can't push things to your phone anymore. Anyway, a hurdle that=
can be jumped if/when it becomes an issue.
>=20
--Apple-Mail-471BA261-CD5F-480F-89A2-32F8B652507C
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: 7bit
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Paul,</div><div><br></div><div>The issue is in the establishment of trust. Anyone can broadcast the initial information.<br><br>e</div><div><br>On Feb 5, 2015, at 2:01 PM, Paul Puey <<a href="mailto:paul@airbitz.co">paul@airbitz.co</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">The broadcast is ONLY done when the wallet is in Receive mode. Same as when the QR code is visible. The use of the *Name* section is specifically so that a recipient can broadcast their name/handle. Not so the recipient would broadcast the name of the Sender.</div><div class="gmail_extra">
<br><div class="gmail_quote">On Thu, Feb 5, 2015 at 12:50 PM, Mike Hearn <span dir="ltr"><<a href="mailto:mike@plan99.net" target="_blank">mike@plan99.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm imagining myself walking around broadcasting my photo and MAC<br>
address while hucksters push payment requests to me for approval</blockquote><div><br></div><div>I hate to break it to you, but you broadcast a photo of your face every time you walk outside ;)</div><div><br></div><div>Bluetooth MAC addresses are random, they aren't useful identifiers. If someone can see you, a face is a far more uniquely identifying thing than a MAC.</div><div><br></div><div>"Payment spam" might be a problem. I can imagine a wallet requiring that such requests are signed and then spammers can be blacklisted in the usual fashion so they can't push things to your phone anymore. Anyway, a hurdle that can be jumped if/when it becomes an issue.</div></div></div></div>
</blockquote></div><br></div>
</blockquote></body></html>
--Apple-Mail-471BA261-CD5F-480F-89A2-32F8B652507C--
|
