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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1VLuWD-0005xy-9q
for bitcoin-development@lists.sourceforge.net;
Tue, 17 Sep 2013 12:36:37 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.41 as permitted sender)
client-ip=209.85.214.41; envelope-from=mh.in.england@gmail.com;
helo=mail-bk0-f41.google.com;
Received: from mail-bk0-f41.google.com ([209.85.214.41])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VLuWC-0000rl-Af
for bitcoin-development@lists.sourceforge.net;
Tue, 17 Sep 2013 12:36:37 +0000
Received: by mail-bk0-f41.google.com with SMTP id na10so2211320bkb.28
for <bitcoin-development@lists.sourceforge.net>;
Tue, 17 Sep 2013 05:36:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.205.35.15 with SMTP id su15mr29004177bkb.21.1379421389333;
Tue, 17 Sep 2013 05:36:29 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.204.72.69 with HTTP; Tue, 17 Sep 2013 05:36:29 -0700 (PDT)
In-Reply-To: <2BC93E25-27D2-474E-842D-6684E96E9472@grabhive.com>
References: <9179D240-EE7E-41A4-AA59-7C96246D8CFB@grabhive.com>
<AFD93558-684C-497C-ADAF-D031095EC2CE@gmail.com>
<82E79EB0-49D6-492A-AE4A-6A786C7B0AAA@grabhive.com>
<3B80F433-9039-459B-BC96-A56786DEF6C3@grabhive.com>
<CANEZrP3srw4AhtYkM60NBcWYSqEib=wB7Yj4YtqaufW3xd9_0Q@mail.gmail.com>
<2BC93E25-27D2-474E-842D-6684E96E9472@grabhive.com>
Date: Tue, 17 Sep 2013 14:36:29 +0200
X-Google-Sender-Auth: yYRCXQhs7WKfwz-lUDvROMMO9iM
Message-ID: <CANEZrP2Ewq4+xT+FCaB_U64QNSW-QA6SooUus+Ad0=DNbh-erA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wendell <w@grabhive.com>
Content-Type: multipart/alternative; boundary=bcaec52c5b27e86bad04e6939173
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
0.0 HTML_OBFUSCATE_05_10 BODY: Message is 5% to 10% HTML obfuscation
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: 1VLuWC-0000rl-Af
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Simple contacts exchange (was: Social
network integration (brainstorm))
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: Tue, 17 Sep 2013 12:36:37 -0000
--bcaec52c5b27e86bad04e6939173
Content-Type: text/plain; charset=UTF-8
The payment protocol doesn't *require* signed certificates, it just gives
the option of using them.
However if you don't have some kind of cryptographic proof of identity,
what stops me putting your name and face into my payment requests and
claiming to be you?
--bcaec52c5b27e86bad04e6939173
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">The payment protocol doesn't <i>require</i>=C2=A0signe=
d certificates, it just gives the option of using them.<div><br></div><div>=
However if you don't have some kind of cryptographic proof of identity,=
what stops me putting your name and face into my payment requests and clai=
ming to be you?</div>
<div><br></div></div>
--bcaec52c5b27e86bad04e6939173--
|
