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-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1VdtxV-0006XW-AW
for bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 03:39:09 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.179 as permitted sender)
client-ip=209.85.217.179; envelope-from=melvincarvalho@gmail.com;
helo=mail-lb0-f179.google.com;
Received: from mail-lb0-f179.google.com ([209.85.217.179])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VdtxS-0003H8-HD
for bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 03:39:09 +0000
Received: by mail-lb0-f179.google.com with SMTP id w6so7169910lbh.24
for <bitcoin-development@lists.sourceforge.net>;
Tue, 05 Nov 2013 19:38:59 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.202.194 with SMTP id kk2mr1124740lbc.2.1383709139732;
Tue, 05 Nov 2013 19:38:59 -0800 (PST)
Received: by 10.112.159.233 with HTTP; Tue, 5 Nov 2013 19:38:59 -0800 (PST)
In-Reply-To: <52756B2E.7030505@corganlabs.com>
References: <20131102050144.5850@gmx.com>
<52756B2E.7030505@corganlabs.com>
Date: Wed, 6 Nov 2013 04:38:59 +0100
Message-ID: <CAKaEYhLn3+CwJ-vvuDQ9+A8H2g6cnn4HpRp++_fmsrcnj5EkzQ@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Johnathan Corgan <johnathan@corganlabs.com>
Content-Type: multipart/alternative; boundary=001a11c37232bf11f504ea79e33d
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: doubleclick.net]
-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
(melvincarvalho[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: 1VdtxS-0003H8-HD
Cc: bitcoingrant@gmx.com,
Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Message Signing based authentication
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: Wed, 06 Nov 2013 03:39:09 -0000
--001a11c37232bf11f504ea79e33d
Content-Type: text/plain; charset=ISO-8859-1
On 2 November 2013 22:14, Johnathan Corgan <johnathan@corganlabs.com> wrote:
> On 11/01/2013 10:01 PM, bitcoingrant@gmx.com wrote:
>
> > Server provides a token for the client to sign.
>
> Anyone else concerned about signing an arbitrary string? Could be a
> hash of $EVIL_DOCUMENT, no? I'd want to XOR the string with my own
> randomly generated nonce, sign that, then pass the nonce and the
> signature back to the server for verification.
>
Good point.
There are actually times you may want to sign a transaction.
There's a little know HTTP code, 402, "Payment Required". We should really
start using this at some point ...
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Reserved for future use.[2] The original intention was that this code might
be used as part of some form of digital cash or micropayment scheme, but
that has not happened, and this code is not usually used. As an example of
its use, however, Apple's defunct MobileMe service generated a 402 error if
the MobileMe account was delinquent.[citation needed] In addition, YouTube
uses this status if a particular IP address has made excessive requests,
and requires the person to enter a CAPTCHA.
>
> --
> Johnathan Corgan, Corgan Labs
> SDR Training and Development Services
> http://corganlabs.com
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a11c37232bf11f504ea79e33d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 2 November 2013 22:14, Johnathan Corgan <span dir=3D"ltr"><<a=
href=3D"mailto:johnathan@corganlabs.com" target=3D"_blank">johnathan@corga=
nlabs.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">On 11/0=
1/2013 10:01 PM, <a href=3D"mailto:bitcoingrant@gmx.com">bitcoingrant@gmx.c=
om</a> wrote:<br>
<br>
> Server provides a token for the client to sign.<br>
<br>
</div>Anyone else concerned about signing an arbitrary string? =A0Could be =
a<br>
hash of $EVIL_DOCUMENT, no? =A0I'd want to XOR the string with my own<b=
r>
randomly generated nonce, sign that, then pass the nonce and the<br>
signature back to the server for verification.<br></blockquote><div><br></d=
iv><div>Good point.<br><br></div><div>There are actually times you may want=
to sign a transaction.<br><br></div><div>There's a little know HTTP co=
de, 402, "Payment Required".=A0 We should really start using this=
at some point ...<br>
<br><a href=3D"http://en.wikipedia.org/wiki/List_of_HTTP_status_codes">http=
://en.wikipedia.org/wiki/List_of_HTTP_status_codes</a><br><br>Reserved for =
future use.[2] The original intention was that this code might be used as p=
art of some form of digital cash or micropayment scheme, but that has not h=
appened, and this code is not usually used. As an example of its use, howev=
er, Apple's defunct MobileMe service generated a 402 error if the Mobil=
eMe account was delinquent.[citation needed] In addition, YouTube uses this=
status if a particular IP address has made excessive requests, and require=
s the person to enter a CAPTCHA.<br>
</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=3D""><font color=3D"#888888"><br>
--<br>
Johnathan Corgan, Corgan Labs<br>
SDR Training and Development Services<br>
<a href=3D"http://corganlabs.com" target=3D"_blank">http://corganlabs.com</=
a><br>
</font></span><br>---------------------------------------------------------=
---------------------<br>
Android is increasing in popularity, but the open development platform that=
<br>
developers love is also attractive to malware creators. Download this white=
<br>
paper to learn more about secure code signing practices that can help keep<=
br>
Android apps secure.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D65839951&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D65839951&iu=3D/4140/ostg.clktrk</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>
<br></blockquote></div><br></div></div>
--001a11c37232bf11f504ea79e33d--
|
