From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vcar2-0001am-I9 for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 13:03:04 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.169 as permitted sender) client-ip=209.85.214.169; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f169.google.com; Received: from mail-ob0-f169.google.com ([209.85.214.169]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vcar1-00028B-LG for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 13:03:04 +0000 Received: by mail-ob0-f169.google.com with SMTP id uz6so5628534obc.28 for ; Sat, 02 Nov 2013 06:02:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.142.8 with SMTP id rs8mr6347881oeb.34.1383397378252; Sat, 02 Nov 2013 06:02:58 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.156.42 with HTTP; Sat, 2 Nov 2013 06:02:58 -0700 (PDT) In-Reply-To: <20131102050144.5850@gmx.com> References: <20131102050144.5850@gmx.com> Date: Sat, 2 Nov 2013 14:02:58 +0100 X-Google-Sender-Auth: swO3bMtuPWpDFpw-Fb9iPFXpcjo Message-ID: From: Mike Hearn To: bitcoingrant@gmx.com Content-Type: multipart/alternative; boundary=047d7b33cd7450651404ea314db3 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 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] 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: 1Vcar1-00028B-LG Cc: Bitcoin Dev 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 13:03:04 -0000 --047d7b33cd7450651404ea314db3 Content-Type: text/plain; charset=UTF-8 On Sat, Nov 2, 2013 at 6:01 AM, wrote: > 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://pilif.github.io/2008/05/why-is-nobody-using-ssl-client-certificates/ --047d7b33cd7450651404ea314db3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sat, Nov 2, 2013 at 6:01 AM, <bitcoingrant@gmx.com= > wrote:

In brief, the authentication work as follows:

=C2=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.


--047d7b33cd7450651404ea314db3--