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
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WR1JA-00013z-GK
for bitcoin-development@lists.sourceforge.net;
Fri, 21 Mar 2014 15:24:32 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.177 as permitted sender)
client-ip=209.85.214.177; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f177.google.com;
Received: from mail-ob0-f177.google.com ([209.85.214.177])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WR1J8-0002S6-98
for bitcoin-development@lists.sourceforge.net;
Fri, 21 Mar 2014 15:24:32 +0000
Received: by mail-ob0-f177.google.com with SMTP id wo20so2559724obc.36
for <bitcoin-development@lists.sourceforge.net>;
Fri, 21 Mar 2014 08:24:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.174.170 with SMTP id bt10mr33800333oec.47.1395415464933;
Fri, 21 Mar 2014 08:24:24 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Fri, 21 Mar 2014 08:24:24 -0700 (PDT)
In-Reply-To: <lghlbp$pef$1@ger.gmane.org>
References: <lc5hmg$1jh$1@ger.gmane.org> <leuunm$tjk$1@ger.gmane.org>
<CANEZrP3nQfvDArKTRgje0Cus4G2JD_zpxSjA3fXfxM2TNAP80Q@mail.gmail.com>
<CALDj+BafD+6KTNcYDBEu5gNPzYozSkiC-JCxrY-PzXL2DYBRsw@mail.gmail.com>
<lge7lv$3mf$1@ger.gmane.org>
<CALDj+BZRsXnU5w=1B+01PDfMPY-7zqU3GP_52vr9wknEdTJ59Q@mail.gmail.com>
<lgh1q8$1dc$1@ger.gmane.org>
<CALDj+Bb=CR1pL0Ze1M6k22wfQM1bL6-w+EyipJQWc1OHhAY0rg@mail.gmail.com>
<lghlbp$pef$1@ger.gmane.org>
Date: Fri, 21 Mar 2014 16:24:24 +0100
X-Google-Sender-Auth: iqNk5Ft3XnrSEpKIPJTItl3-kDo
Message-ID: <CANEZrP3t1t2+qgE6fPR3zQ=x5c=XU+mnJEazcT=HOWu91KnxUg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=047d7bd6c52c19fdfc04f51f7b51
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: 1WR1J8-0002S6-98
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments
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, 21 Mar 2014 15:24:32 -0000
--047d7bd6c52c19fdfc04f51f7b51
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
SPDY requires SSL and is even more complex than HTTP.
Really, the current protocol we've got (length prefixed protobufs) is just
fine except for the lack of encryption/authentication. For that you need to
do ECDH to establish a shared AES session key, and MAC each packet. Like I
said, it's not entirely trivial which is why it's worth trying SSL too, but
it's also not a massive effort.
On Fri, Mar 21, 2014 at 4:20 PM, Andreas Schildbach
<andreas@schildbach.de>wrote:
> On 03/21/2014 02:54 PM, Alex Kotenko wrote:
>
> > > I wonder how complex it would be to implement HTTP-over-Bluetooth=
.
> Not
> > > like I'm willing to do that now, but HTTP is well known and prove=
n
> > to be
> > > quite good for tasks like this, so in theory it would be handy to
> have
> > > such capacities in here.
> >
> > Thought of that as well. On the other hand, HTTP might be overkill
> and
> > we inherit its potential downsides as well.
> >
> > =E2=80=8BIt definitely is an overkill. Don't think we should do it now =
unless we
> > will see later during implementation that we really have to.
>
> Btw. we could also consider SPDY. I'm not sure about the advantages, but
> its probably quicker and leaner.
>
>
>
>
>
> -------------------------------------------------------------------------=
-----
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and thei=
r
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7bd6c52c19fdfc04f51f7b51
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">SPDY requires SSL and is even more complex than HTTP.<div>=
<br></div><div>Really, the current protocol we've got (length prefixed =
protobufs) is just fine except for the lack of encryption/authentication. F=
or that you need to do ECDH to establish a shared AES session key, and MAC =
each packet. Like I said, it's not entirely trivial which is why it'=
;s worth trying SSL too, but it's also not a massive effort.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
Mar 21, 2014 at 4:20 PM, Andreas Schildbach <span dir=3D"ltr"><<a href=
=3D"mailto:andreas@schildbach.de" target=3D"_blank">andreas@schildbach.de</=
a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 03/21/2014 02:54 PM, Alex Kotenko wrote:<=
br>
<br>
> =C2=A0 =C2=A0 > I wonder how complex it would be to implement HTTP-=
over-Bluetooth. Not<br>
> =C2=A0 =C2=A0 > like I'm willing to do that now, but HTTP is we=
ll known and proven<br>
> =C2=A0 =C2=A0 to be<br>
> =C2=A0 =C2=A0 > quite good for tasks like this, so in theory it wou=
ld be handy to have<br>
> =C2=A0 =C2=A0 > such capacities in here.<br>
><br>
> =C2=A0 =C2=A0 Thought of that as well. On the other hand, HTTP might b=
e overkill and<br>
> =C2=A0 =C2=A0 we inherit its potential downsides as well.<br>
><br>
> =E2=80=8BIt definitely is an overkill. Don't think we should do it=
now unless we<br>
> will see later during implementation that we really have to.<br>
<br>
Btw. we could also consider SPDY. I'm not sure about the advantages, bu=
t<br>
its probably quicker and leaner.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--047d7bd6c52c19fdfc04f51f7b51--
|
