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
|
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 <elarch@gmail.com>) id 1WW6YJ-0005XI-Hf
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 16:01:11 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.47 as permitted sender)
client-ip=209.85.215.47; envelope-from=elarch@gmail.com;
helo=mail-la0-f47.google.com;
Received: from mail-la0-f47.google.com ([209.85.215.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WW6YI-000119-Jm
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 16:01:11 +0000
Received: by mail-la0-f47.google.com with SMTP id pn19so2600083lab.6
for <bitcoin-development@lists.sourceforge.net>;
Fri, 04 Apr 2014 09:01:03 -0700 (PDT)
X-Received: by 10.112.139.166 with SMTP id qz6mr8817126lbb.13.1396627263896;
Fri, 04 Apr 2014 09:01:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.31.165 with HTTP; Fri, 4 Apr 2014 09:00:43 -0700 (PDT)
In-Reply-To: <CANEZrP3exbwE0AuZCXQNEC-UoZ0BmTHTpSG6rZsjbwmpKahtCQ@mail.gmail.com>
References: <CA+WZAEp3HsW5ESGUZ7YfR1MZXGC5jd+LucUt_MUP8K94Xwhuhg@mail.gmail.com>
<CANEZrP0KVyp2Va7Wyy=t0qYkLNK9BDUaSzBfuzQss+=weLJ1Fw@mail.gmail.com>
<CA+WZAEqYKv8T1OMCKhOJvf5FAy=WujJ=OhtsYP9aBf=4ZPNxmw@mail.gmail.com>
<CANEZrP0DTYqobECBbw6eZqdk+-TR_2jhBtOviN08r31EQGmZHQ@mail.gmail.com>
<CANEZrP2Z5x0_kOQ=8-BMzbmi9=D=ou=s3dgEksMA5F84BHSt9A@mail.gmail.com>
<CA+WZAEqREDkDvmhM7AY+Ju3fkm3uOGm39Ef9+SYoEr43ybbg2Q@mail.gmail.com>
<CAJna-Hhz+K0iw4b8DDp5tNpQg6nJABKmu__aDbgT9M26PJ9tAg@mail.gmail.com>
<CA+WZAErh6M6BV1imAXZaHQjX+5RKtj7Ma7_-+5KW9BpLw354Sg@mail.gmail.com>
<CANEZrP3exbwE0AuZCXQNEC-UoZ0BmTHTpSG6rZsjbwmpKahtCQ@mail.gmail.com>
From: =?ISO-8859-1?Q?Eric_Larchev=EAque?= <elarch@gmail.com>
Date: Fri, 4 Apr 2014 18:00:43 +0200
Message-ID: <CA+WZAEpWFb5jRE+W-BaJsNAWNJgWhuXu5gTYk+9ZwQ7qQ6FsUQ@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=001a11c26692f2c1e204f6399fb9
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
(elarch[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: 1WW6YI-000119-Jm
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 16:01:11 -0000
--001a11c26692f2c1e204f6399fb9
Content-Type: text/plain; charset=ISO-8859-1
>
> Hmmm, well TREZOR requires a web plugin. So if nobody installs plugins
> then we have a problem :) But regardless, actually like I said, you don't
> need a plugin. Browsers do it all already. With the <keygen> tag they even
> create a private key and upload the public part to be signed for you, it's
> seamless for the user. I wanted to give you a link to a demo site, but I
> can't find it anymore :(
>
>
If you buy a TREZOR you will of course install the plugin :)
What I mean is that normal people are lazy : if the solution is already in
their hand they will use it, if they need to install/configure something,
they won't do it.
I'm not trying to propose a solution to solve the auth on the web, but to
ease the sign up / login on the Bitcoin ecosystem websites and apps.
More sign ups to new services (whatever the services) = more usage =
expanding ecosystem = more global value to Bitcoin
Wallets are a key element of the equation because :
- everyone has one (desktop or mobile)
- everyone (in theory) has already taken all steps to backup and secure
their keys
- id yourself with a Bitcoin address often makes sense on a Bitcoin related
service
Eric
--001a11c26692f2c1e204f6399fb9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr">Hmmm, well TREZOR requires a we=
b plugin. So if nobody installs plugins then we have a problem :) But regar=
dless, actually like I said, you don't need a plugin. Browsers do it al=
l already. With the <keygen> tag they even create a private key and u=
pload the public part to be signed for you, it's seamless for the user.=
I wanted to give you a link to a demo site, but I can't find it anymor=
e :(<div>
<br></div></div></blockquote><div><br></div><div>If you buy a TREZOR you wi=
ll of course install the plugin :)</div><div><br></div><div>What I mean is =
that normal people are lazy : if the solution is already in their hand they=
will use it, if they need to install/configure something, they won't d=
o it.</div>
<div><br></div><div>I'm not trying to propose a solution to solve the a=
uth on the web, but to ease the sign up / login on the Bitcoin ecosystem we=
bsites and apps.</div><div>More sign ups to new services (whatever the serv=
ices) =3D more usage =3D expanding ecosystem =3D more global value to Bitco=
in</div>
<div><br></div><div>Wallets are a key element of the equation because :</di=
v><div>- everyone has one (desktop or mobile)</div><div>- everyone (in theo=
ry) has already taken all steps to backup and secure their keys</div><div>
- id yourself with a Bitcoin address often makes sense on a Bitcoin related=
service</div><div><br></div><div>Eric</div></div></div></div>
--001a11c26692f2c1e204f6399fb9--
|
