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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <eric@voskuil.org>) id 1YJTw6-0006Zl-Cp
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 21:26:06 +0000
X-ACL-Warn:
Received: from mail-pd0-f179.google.com ([209.85.192.179])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YJTw5-0006G3-J9
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 21:26:06 +0000
Received: by pdjy10 with SMTP id y10so10127143pdj.7
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Feb 2015 13:26:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
:cc:subject:references:in-reply-to:content-type;
bh=D6UbBDOaq8Tb7pvwbHD70Gh/J5t9jzaJ4xqBooWyWVI=;
b=QKx+ESkmFdObBr3bEU0TSeql+0KSGkLFdKmkUrHSN+L2K+P/2J8ogyf2PqLsAbhPBM
SqdavGYLlu2JUIQJG3rFvAErHx0uHKi8C7BrmP35bxkHOcBhJI/h18X6SFZdlqUsg398
D5Di23MjatuTObFIFJA0Dl+4oBBBdYaC0NGPL74FQ9jBqbYsDpp4KXLOHBX0mskRide9
z2Ai6eDEpmUjZdYe9HhrSocIo4wG50aUlZsCePSjYdqQFJwUJcBruroDA+h4gtI6pGTc
kLi3bY6r9QLm4eqOh7d4nR7f9/rC5S0v6ZOaKKdjvEFuBhGIurZik7ioU3o3jHTFtgdQ
/duA==
X-Gm-Message-State: ALoCoQnfrVnfZo5s11jNXwHXUgpIMoCh6xUxNhAa4F06ui/mzRREB9vRmOjh0e8ydHFuzAce2dVu
X-Received: by 10.70.95.35 with SMTP id dh3mr89423pdb.91.1423169972638;
Thu, 05 Feb 2015 12:59:32 -0800 (PST)
Received: from [10.0.1.3] (c-50-135-46-157.hsd1.wa.comcast.net.
[50.135.46.157])
by mx.google.com with ESMTPSA id fg6sm5953548pdb.24.2015.02.05.12.59.31
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 05 Feb 2015 12:59:32 -0800 (PST)
Message-ID: <54D3D9C4.9090400@voskuil.org>
Date: Thu, 05 Feb 2015 12:59:48 -0800
From: Eric Voskuil <eric@voskuil.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Mike Hearn <mike@plan99.net>
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>
In-Reply-To: <CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1YJTw5-0006G3-J9
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:26:06 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
On 02/05/2015 12:50 PM, Mike Hearn 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=
> time you walk outside ;)
>=20
> 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.
Interesting take on privacy. But the market will of course decide.
Would the merchant be broadcasting payment requests in the clear, or
would they be encrypted with a public key of the spender?
> "Payment spam" might be a problem. I can imagine a wallet requiring tha=
t
> 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.
Not sure I'd shoot for a system that's guaranteed to require PKI with
blacklisting and spam filtering.
e
--CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU09nEAAoJEDzYwH8LXOFO8t4H+wQd9LW+BIVauUw2kgQytuOw
TpVIf0UtgSyTQWYJHeloj6WFMVeXAHZfBDZanWnx6vsDhwSRihX7pWwUiH907fkX
3A/wBiJfzB1q11rHdyv9AQh9UswklLVYxklFJ1cQrYhIlqXIMpMEkiDZU3Be3a+t
hCPsYpnU2Yogzg3pkqe8cf7pGddXA3UWg/eBb7j2rYPsfX8q7EPUJ8rt26unoq/N
skNRbdGn8+eCUCF/paDtFjOj7IHSrhsq22UFiwtHVUJldLsmfLlgRH7KR/ukD5Cf
KTGPW8Xyf/yUpA+XSco/vuPCljKd1qbBJ9wM5h2hQBm+pcUktde+NfAwOFN5PTI=
=h5gf
-----END PGP SIGNATURE-----
--CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP--
|
