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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1UVX8B-00040I-8K
for bitcoin-development@lists.sourceforge.net;
Fri, 26 Apr 2013 01:07:19 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.83.49 as permitted sender)
client-ip=74.125.83.49; envelope-from=gavinandresen@gmail.com;
helo=mail-ee0-f49.google.com;
Received: from mail-ee0-f49.google.com ([74.125.83.49])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UVX86-0000wP-54
for bitcoin-development@lists.sourceforge.net;
Fri, 26 Apr 2013 01:07:19 +0000
Received: by mail-ee0-f49.google.com with SMTP id d4so1472823eek.8
for <bitcoin-development@lists.sourceforge.net>;
Thu, 25 Apr 2013 18:07:07 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.15.26.6 with SMTP id m6mr47064443eeu.4.1366938427824; Thu,
25 Apr 2013 18:07:07 -0700 (PDT)
Received: by 10.223.96.132 with HTTP; Thu, 25 Apr 2013 18:07:07 -0700 (PDT)
In-Reply-To: <CA+CODZFpS2DWaC0KRghymOXKQdNhhxAty_5eW0XZJ8Sg5s1bGQ@mail.gmail.com>
References: <mailman.38128.1366844895.4905.bitcoin-development@lists.sourceforge.net>
<20130425095855.GA30535@crunch>
<CANEZrP3EhS3-HnPT_exc9MjZn-ywZggSzqSHPzHU5J2EZuLQtg@mail.gmail.com>
<20130425102853.GA31573@crunch>
<CANEZrP1343gX-utnbO16Z6axMDMmvYpiGXW8_Vc-yec03ip=1g@mail.gmail.com>
<FDF215AE-F9A4-4EE3-BDC9-0A4EF027423A@swipeclock.com>
<CANEZrP0FS5CZaqEEwCZM-nfPB9D2TfC_moX3BE+TEnfWtc=aOg@mail.gmail.com>
<CA+CODZFpS2DWaC0KRghymOXKQdNhhxAty_5eW0XZJ8Sg5s1bGQ@mail.gmail.com>
Date: Thu, 25 Apr 2013 21:07:07 -0400
Message-ID: <CABsx9T3egz=7YNOrgx7WsfSthLfN2gfE60YfPEv8096vyErBqg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Jeremy Spilman <jeremy.spilman@gmail.com>
Content-Type: multipart/alternative; boundary=089e0168144c6bc97204db392788
X-Spam-Score: -0.6 (/)
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
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1UVX86-0000wP-54
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Cold Signing Payment Requests
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: Fri, 26 Apr 2013 01:07:19 -0000
--089e0168144c6bc97204db392788
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Apr 25, 2013 at 3:12 PM, Jeremy Spilman <jeremy.spilman@gmail.com>wrote:
> Right now I'm leaning towards writing a prototype using a single cert with
> a fingerprint of PubKey in the Subject Alternate Name, and getting PubKey
> and InvoiceID in the Payment Request. Gavin, would the best way to work on
> this be to just fork your code on Github?
>
As usual, our bottleneck is code review / testing, so it would be nice if
you spent some time reviewing code and helping test v0.9 so we can actually
ship a v1 sometime in the next several months before you start working on a
v2.
--
--
Gavin Andresen
--089e0168144c6bc97204db392788
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Thu, Apr 25, 2013 at 3:12 PM, Jeremy Spilman <span dir=3D"ltr"><<a hr=
ef=3D"mailto:jeremy.spilman@gmail.com" target=3D"_blank">jeremy.spilman@gma=
il.com</a>></span> wrote:<br><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<div dir=3D"ltr"><div>Right now I'm leaning towards writing a prototype=
using a single cert with a fingerprint of PubKey in the Subject Alternate =
Name, and getting PubKey and InvoiceID in the Payment Request. =A0Gavin, wo=
uld the best way to work on this be to just fork your code on Github?</div>
<div></div></div></blockquote></div><div><br></div>As usual, our bottleneck=
is code review / testing, so it would be nice if you spent some time revie=
wing code and helping test v0.9 so we can actually ship a v1 sometime in th=
e next several months before you start working on a v2.<div>
<div><br></div>-- <br>--<br>Gavin Andresen<br>
</div><div><br></div>
--089e0168144c6bc97204db392788--
|
