Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.49 as permitted sender)
	client-ip=209.85.215.49; envelope-from=elarch@gmail.com;
	helo=mail-la0-f49.google.com; 
MIME-Version: 1.0
From: =?ISO-8859-1?Q?Eric_Larchev=EAque?= <elarch@gmail.com>
Date: Fri, 4 Apr 2014 14:15:56 +0200
Message-ID: <CA+WZAEp3HsW5ESGUZ7YfR1MZXGC5jd+LucUt_MUP8K94Xwhuhg@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a113484bc04fca104f6367cdc
Subject: [Bitcoin-development] Draft BIP for seamless website authentication
	using Bitcoin address
Precedence: list

--001a113484bc04fca104f6367cdc
Content-Type: text/plain; charset=ISO-8859-1

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 being
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

--001a113484bc04fca104f6367cdc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<br><br>I&#39;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">https://=
github.com/bitid/bitid/blob/master/BIP_draft.md</a><br>

<br>Demo website :<br><a href=3D"http://bitid-demo.herokuapp.com/">http://b=
itid-demo.herokuapp.com/</a><br><br>Classical password authentication is an=
 insecure process that could be solved with public key cryptography. The pr=
oblem is that it theoretically offloads a lot of complexity and responsibil=
ity on the user. Managing private keys securely is complex. However this co=
mplexity is already being addressed in the Bitcoin ecosystem. So doing publ=
ic key authentication is practically a free lunch to bitcoiners.<br>

<div><br></div><div>I&#39;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 &quot;process&quot; 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">elarch@gmail.com</a></=
div>

<div><br></div></div></div>

--001a113484bc04fca104f6367cdc--