From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VcUAS-0008A4-KQ for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 05:54:40 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([192.3.11.21]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1VcUAR-0005eK-Jg for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 05:54:40 +0000 Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:222:4dff:fe50:4c49]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id CCCE11083790 for ; Sat, 2 Nov 2013 05:54:38 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Sat, 2 Nov 2013 05:54:28 +0000 User-Agent: KMail/1.13.7 (Linux/3.10.15-gentoo; KDE/4.10.5; x86_64; ; ) References: <20131102050144.5850@gmx.com> In-Reply-To: <20131102050144.5850@gmx.com> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201311020554.31403.luke@dashjr.org> X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 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: bitcoingrant.org] X-Headers-End: 1VcUAR-0005eK-Jg 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 05:54:40 -0000 On Saturday, November 02, 2013 5:01:43 AM bitcoingrant@gmx.com wrote: > 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. Congratulations! You've reinvented what Eligius and Bitcoin-OTC have been doing for years! :) There's no reason to ask the user to provide the address every time, though... Luke