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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1W2jtv-0008Cf-QV
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jan 2014 15:58:07 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.41 as permitted sender)
client-ip=209.85.219.41; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f41.google.com;
Received: from mail-oa0-f41.google.com ([209.85.219.41])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W2jtu-0005w4-Pi
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jan 2014 15:58:07 +0000
Received: by mail-oa0-f41.google.com with SMTP id i4so7231162oah.0
for <bitcoin-development@lists.sourceforge.net>;
Mon, 13 Jan 2014 07:58:01 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.143.103 with SMTP id sd7mr1421463obb.70.1389628681380;
Mon, 13 Jan 2014 07:58:01 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.99.112 with HTTP; Mon, 13 Jan 2014 07:58:01 -0800 (PST)
In-Reply-To: <20140113133746.GI38964@giles.gnomon.org.uk>
References: <20140106120338.GA14918@savin>
<op.w9c5o7vgyldrnw@laptop-air.hsd1.ca.comcast.net>
<20140110102037.GB25749@savin>
<op.w9kkxcityldrnw@laptop-air.hsd1.ca.comcast.net>
<CABsx9T2G=yqSUGr0+Ju5-z9P++uS20AwLC+c3DnFMHtcQjQK6w@mail.gmail.com>
<CAAS2fgTz0TaGhym_35V3N2-vHVzU9BeuV8q+QJjwh5bg77FEZg@mail.gmail.com>
<CANEZrP0huBWqgvQik9Yc26Tu4CwR0VSXcfC+qfzsZqvoU4VJGA@mail.gmail.com>
<20140113133746.GI38964@giles.gnomon.org.uk>
Date: Mon, 13 Jan 2014 16:58:01 +0100
X-Google-Sender-Auth: k7Rd2Bxo1HyCPdndIm6BPGVhe_U
Message-ID: <CANEZrP1KAVhi_-cxCYe0rR9LUSYJ8MyW8=6eSJZ65FeY5ZJNuQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Roy Badami <roy@gnomon.org.uk>
Content-Type: multipart/alternative; boundary=e89a8ff1ce9eec69d704efdc2323
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1W2jtu-0005w4-Pi
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Stealth Addresses
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: Mon, 13 Jan 2014 15:58:08 -0000
--e89a8ff1ce9eec69d704efdc2323
Content-Type: text/plain; charset=UTF-8
On Mon, Jan 13, 2014 at 2:37 PM, Roy Badami <roy@gnomon.org.uk> wrote:
> That does require trusting the third party not to later tamper with
> the payment request, though.
You have to trust the billboard owner too. If you're relying on a third
party to relay a payment instruction, that will always be an issue, hence
the signing.
Signing a payment request for an individual is easy, anyway, depending on
the kind of ID you want. If you want to sign with an email address, just go
here with a browser like Chrome/Safari/IE that uses the system keystore:
http://www.comodo.com/home/email-security/free-email-certificate.php
They'll send you an email, you click the link to verify, and a cert will be
generated and installed by your web browser. It's actually easier than
signing up for a website. There are lots of other places that do it for
free too, I just picked the first one from a google search for [free email
certificate].
Once you've got that in your keystore, a wallet app can quite easily be
told to sign payment requests with your email address.
For a billboard I guess you'd probably be an organisation or company
instead, though an email address can work there too as long as you have a
well known domain name.
--e89a8ff1ce9eec69d704efdc2323
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Jan 13, 2014 at 2:37 PM, Roy Badami <span dir=3D"ltr"><<a href=3D"ma=
ilto:roy@gnomon.org.uk" target=3D"_blank">roy@gnomon.org.uk</a>></span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(34,34,34)">That=
does require trusting the third party not to later tamper with</span><br>
</div>
the payment request, though.</blockquote><div><br></div><div>You have to tr=
ust the billboard owner too. If you're relying on a third party to rela=
y a payment instruction, that will always be an issue, hence the signing.</=
div>
<div><br></div><div>Signing a payment request for an individual is easy, an=
yway, depending on the kind of ID you want. If you want to sign with an ema=
il address, just go here with a browser like Chrome/Safari/IE that uses the=
system keystore:</div>
<div><br></div><div>=C2=A0 =C2=A0<a href=3D"http://www.comodo.com/home/emai=
l-security/free-email-certificate.php">http://www.comodo.com/home/email-sec=
urity/free-email-certificate.php</a><br></div><div><br></div><div>They'=
ll send you an email, you click the link to verify, and a cert will be gene=
rated and installed by your web browser. It's actually easier than sign=
ing up for a website. There are lots of other places that do it for free to=
o, I just picked the first one from a google search for [free email certifi=
cate].</div>
<div><br></div><div>Once you've got that in your keystore, a wallet app=
can quite easily be told to sign payment requests with your email address.=
</div><div><br></div><div>For a billboard I guess you'd probably be an =
organisation or company instead, though an email address can work there too=
as long as you have a well known domain name.</div>
</div></div></div>
--e89a8ff1ce9eec69d704efdc2323--
|
