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 ) id 1VcjDA-0005qi-4s for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 21:58:28 +0000 X-ACL-Warn: Received: from mail-ve0-f181.google.com ([209.85.128.181]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VcjD8-0006xv-QG for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 21:58:28 +0000 Received: by mail-ve0-f181.google.com with SMTP id jz11so573441veb.12 for ; Sat, 02 Nov 2013 14:58:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=WJsuWp8VeSMJo1W8VnVdVsXcOriBjutIWyRtn/1RU9E=; b=KM9+fTJEMVQxcDF33Oa6V34rLopa/zlaPqMbbHMAybuM3eQH7o8ysuBaelaOXG21OC 353AEHUz3pRJIowbJ6xRbx0UyFN753By7e0cFL5P3PfJmRiSP2lP1/oMWYpauLtP7D+f JV/hJBPbvYS4CIhUgBIlnUi0vw6Ie1VD0bTLpA17EbDgEvlx/+MwHkWB1/Cgs1HB5/2B rVIGm6tqUbEqJ7UhfcJl7wKmWXOjQ+cCuTojPZdENWRE/A3orbohoVcnCVPLC33Il9NS ea/TeREmgLQ+sfHZT5eT6lO8ws04i8HfcWIrilBR8SuehPT5amilfwMnin3q65w9Yi4H yEhg== X-Gm-Message-State: ALoCoQkpQ9VfLlYNPuhlqZRiSimIJfpjiFu4Atgs1Ig0QDfMnzUX2uODsbDCeN5nj5J5z2BKeUqD X-Received: by 10.58.217.130 with SMTP id oy2mr806441vec.24.1383429501126; Sat, 02 Nov 2013 14:58:21 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.59.1.2 with HTTP; Sat, 2 Nov 2013 14:57:50 -0700 (PDT) In-Reply-To: <20131102050144.5850@gmx.com> References: <20131102050144.5850@gmx.com> From: slush Date: Sat, 2 Nov 2013 22:57:50 +0100 X-Google-Sender-Auth: gx2dM9KCKPuwJKM5HK4VWeqeCEI Message-ID: To: bitcoingrant@gmx.com Content-Type: multipart/alternative; boundary=047d7bdc051efca53804ea38c776 X-Spam-Score: 1.0 (+) 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: gmx.com] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slush[at]centrum.cz) 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1VcjD8-0006xv-QG Cc: "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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 21:58:28 -0000 --047d7bdc051efca53804ea38c776 Content-Type: text/plain; charset=ISO-8859-1 Glad to see that there are more and more people wanting to replace passwords with digital signatures. Although such method has been already used on other websites like Eligius or bitcoin-otc, I dont think theres any standard way to doing so yet. Two comments to your proposal: A) message-to-be-signed need to be carefully composed to be both structured and human readable. It should contain at least: Desired username/identity handler Server identifier (url) Timestamp to prevent replay attack Server challenge Then the user can see what he's signing, instead of signing some binary blob which can contain some evil data. B) Same structured data should be a part of html page in some header tag, ideally signed by server certificate to confirm that the request is valid. Then the login request can be processed by machine automatically, without a need of copy&paste by a user. Slush On Sat, Nov 2, 2013 at 6:01 AM, wrote: > Passwords are inefficient by design: frequently we hear news from Sony, > Square Enix, Adobe, and various others about passwords being compromised, > databases being copied and stolen. This story remains true in the Bitcoin > space. In light of the recent Bitcointalk forum breach echoes an increasing > need for passwords to become a thing of the past. > > > > In celebration of the 5 year anniversary of the Bitcoin whitepaper, we are > delighted to introduce the Message Signing based authentication method. > > > > In brief, the authentication work as follows: > > > > Server provides a token for the client to sign. > > client passes the signed message and the bitcoin address back to the > server. > > server validates the message and honors the alias (optional) and bitcoin > address as identification. > > > > http://forums.bitcoingrant.org/ > > > > Above is a proof of concept forum that utilize this authentication method. > Following Kerckhoffs's principle, this forum only stores the signed message > and bitcoin address the users provide the first time they use the site, > both are public information. In addition, there is no database, everything > is simply an RSS feed. For the sake of usability we have included a redis > for the sessions, at the cost of additional exposure to potential risks: > users no longer need to sign a token every time they wish to post. > > > > All source code will be available on github in the next few days. > > > > We welcome any feedback or suggestions. > > > > > > ------------------------------------------------------------------------------ > 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 > > --047d7bdc051efca53804ea38c776 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Glad to see that there are more and more people wanting to r= eplace passwords with digital signatures.

Although such method has been already used on other websites like Eligius o= r bitcoin-otc, I dont think theres any standard way to doing so yet.

Two c= omments to your proposal:

A)= message-to-be-signed need to be carefully composed to be both structured a= nd human readable. It should contain at least:
Desired username/identity= handler
Server identifier (url)
Timestamp to prevent replay attack
Server cha= llenge

Then the user can see what he's signing, instead of signing som= e binary blob which can contain some evil data.

B)=
Same structured data should be a part of html page in some header tag, = ideally signed by server certificate to confirm that the request is valid. = Then the login request can be processed by machine automatically, without a= need of copy&paste by a user.

Sl= ush



On Sat, Nov 2, 2013 at 6:01 AM, <bitcoingrant@gmx.com> wrote:

Passwords are ineffici= ent by design: frequently we hear news from Sony, Square Enix, Adobe, and v= arious others about passwords being compromised, databases being copied and= stolen. This story remains true in the Bitcoin space. In light of the rece= nt Bitcointalk forum breach echoes an increasing need for passwords to beco= me a thing of the past.

=A0

In celebration of the 5 year anniversary of the Bitcoi= n whitepaper, we are delighted to introduce the Message Signing based authe= ntication method.

=A0

In brief, the authentication work as follows:

=A0

Server provides a token for the client to sign.=

= client passes the sign= ed message and the bitcoin address back to the server.

= server validates the m= essage and honors the alias (optional) and bitcoin address as identificatio= n.

=A0

http://forums.bitcoingrant.org/

=A0

Above is a proof of concept forum that utilize this au= thentication method. Following Kerckhoffs's principle, this forum only = stores the signed message and bitcoin address the users provide the first t= ime they use the site, both are public information. In addition, there is n= o database, everything is simply an RSS feed. For the sake of usability we = have included a redis for the sessions, at the cost of additional exposure = to potential risks: users no longer need to sign a token every time they wi= sh to post.

=A0

All source code will be available on github in the nex= t few days.

=A0

We welcome any feedback or suggestions.


=A0
-----------------------------------------------------------------------= -------
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<= br> Android apps secure.
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D65839951&iu=3D/4140/ostg.clktrk
___________________= ____________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--047d7bdc051efca53804ea38c776--