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
187
188
189
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
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 1WW3rj-0006fT-NX
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 13:09:03 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.54 as permitted sender)
client-ip=209.85.219.54; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f54.google.com;
Received: from mail-oa0-f54.google.com ([209.85.219.54])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WW3ri-0001Va-F0
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 13:09:03 +0000
Received: by mail-oa0-f54.google.com with SMTP id n16so3523669oag.13
for <bitcoin-development@lists.sourceforge.net>;
Fri, 04 Apr 2014 06:08:57 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.229.228 with SMTP id st4mr19055753oec.16.1396616937081;
Fri, 04 Apr 2014 06:08:57 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Fri, 4 Apr 2014 06:08:57 -0700 (PDT)
In-Reply-To: <CA+WZAEp3HsW5ESGUZ7YfR1MZXGC5jd+LucUt_MUP8K94Xwhuhg@mail.gmail.com>
References: <CA+WZAEp3HsW5ESGUZ7YfR1MZXGC5jd+LucUt_MUP8K94Xwhuhg@mail.gmail.com>
Date: Fri, 4 Apr 2014 15:08:57 +0200
X-Google-Sender-Auth: w8YYK7yl49lpB3VqGTllQzW_xhE
Message-ID: <CANEZrP0KVyp2Va7Wyy=t0qYkLNK9BDUaSzBfuzQss+=weLJ1Fw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?Q?Eric_Larchev=C3=AAque?= <elarch@gmail.com>
Content-Type: multipart/alternative; boundary=001a11362fb06c193204f63738d0
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: 1WW3ri-0001Va-F0
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Draft BIP for seamless website
authentication using Bitcoin address
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, 04 Apr 2014 13:09:04 -0000
--001a11362fb06c193204f63738d0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
This comes up every few months. I think the problem you are trying to solve
is already solved by SSL client certificates, and if you want to help make
them more widespread the programs you need to upgrade are web browsers and
not Bitcoin wallets. There are certainly bits of infrastructure you could
reuse here and there, like perhaps a TREZOR with a custom firmware
extension for really advanced/keen users, but overall Bitcoin and website
authentication are unrelated problems.
On Fri, Apr 4, 2014 at 2:15 PM, Eric Larchev=C3=AAque <elarch@gmail.com> wr=
ote:
> Hello,
>
> I've written a draft BIP description of an authentication protocol based
> on Bitcoin public address.
>
> By authentication we mean to prove to a service/application that we
> control a specific Bitcoin address by signing a challenge, and that all
> related data and settings may securely be linked to our session.
>
> The aim is to greatly facilitate sign ups and logins to services and
> applications, improving the Bitcoin ecosystem as a whole.
>
> https://github.com/bitid/bitid/blob/master/BIP_draft.md
>
> Demo website :
> http://bitid-demo.herokuapp.com/
>
> Classical password authentication is an insecure process that could be
> solved with public key cryptography. The problem is that it theoretically
> offloads a lot of complexity and responsibility on the user. Managing
> private keys securely is complex. However this complexity is already bein=
g
> addressed in the Bitcoin ecosystem. So doing public key authentication is
> practically a free lunch to bitcoiners.
>
> I've formatted the protocol description as a BIP because this is the only
> way to have all major wallets implementing it, and because it completely
> fits in my opinion the BIP "process" category.
>
> Please read it and let me know your thoughts and comments so we can
> improve on this draft.
>
> Eric Larcheveque
> elarch@gmail.com
>
>
>
> -------------------------------------------------------------------------=
-----
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a11362fb06c193204f63738d0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">This comes up every few months. I think the problem you ar=
e trying to solve is already solved by SSL client certificates, and if you =
want to help make them more widespread the programs you need to upgrade are=
web browsers and not Bitcoin wallets. There are certainly bits of infrastr=
ucture you could reuse here and there, like perhaps a TREZOR with a custom =
firmware extension for really advanced/keen users, but overall Bitcoin and =
website authentication are unrelated problems.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Apr 4=
, 2014 at 2:15 PM, Eric Larchev=C3=AAque <span dir=3D"ltr"><<a href=3D"m=
ailto:elarch@gmail.com" target=3D"_blank">elarch@gmail.com</a>></span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Hello,<br><br>I've written a draft BIP description of =
an authentication protocol based on Bitcoin public address.<br><br>By authe=
ntication we mean to prove to a service/application that we control a speci=
fic Bitcoin address by signing a challenge, and that all related data and s=
ettings may securely be linked to our session.<div>
<br></div><div>The aim is to greatly facilitate sign ups and logins to serv=
ices and applications, improving the Bitcoin ecosystem as a whole.<br><br><=
a href=3D"https://github.com/bitid/bitid/blob/master/BIP_draft.md" target=
=3D"_blank">https://github.com/bitid/bitid/blob/master/BIP_draft.md</a><br>
<br>Demo website :<br><a href=3D"http://bitid-demo.herokuapp.com/" target=
=3D"_blank">http://bitid-demo.herokuapp.com/</a><br><br>Classical password =
authentication is an insecure process that could be solved with public key =
cryptography. The problem is that it theoretically offloads a lot of comple=
xity and responsibility on the user. Managing private keys securely is comp=
lex. However this complexity is already being addressed in the Bitcoin ecos=
ystem. So doing public key authentication is practically a free lunch to bi=
tcoiners.<br>
<div><br></div><div>I've formatted the protocol description as a BIP be=
cause this is the only way to have all major wallets implementing it, and b=
ecause it completely fits in my opinion the BIP "process" categor=
y.</div>
<div><br></div><div>Please read it and let me know your thoughts and commen=
ts so we can improve on this draft.<br></div><div><br></div><div>Eric Larch=
eveque</div><div><a href=3D"mailto:elarch@gmail.com" target=3D"_blank">elar=
ch@gmail.com</a></div>
<div><br></div></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
<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>
--001a11362fb06c193204f63738d0--
|
