<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-11-02&#xA;📝 Original message:On Sat, Nov 2, 2013 at 6:01 AM, &lt;bitcoingrant at gmx.com&gt; wrote:&#xA;&#xA;&gt; In brief, the authentication work as follows:&#xA;&gt;&#xA;&gt;&#xA;&gt;&#xA;&gt; Server provides a token for the client to sign.&#xA;&gt;&#xA;&gt; client passes the signed message and the bitcoin address back to the&#xA;&gt; server.&#xA;&gt;&#xA;&gt; server validates the message and honors the alias (optional) and bitcoin&#xA;&gt; address as identification.&#xA;&gt;&#xA;&#xA;http://pilif.github.io/2008/05/why-is-nobody-using-ssl-client-certificates/&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131102/6892fd9d/attachment.html&gt;</html></oembed>