summaryrefslogtreecommitdiff
path: root/74/6ff5a8acaae7654e7d0e58c2ffe5befd4cdd66
blob: 64847489df6c414b2d751806c0c61d8494026440 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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: <CANEZrP2UwEX+u0XCxmaMaRWqVMr+3E63UYnVz9oMubbsiJU+6A@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
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 <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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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, <bitcoingrant@gmx.com> 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

<div dir=3D"ltr">On Sat, Nov 2, 2013 at 6:01 AM,  <span dir=3D"ltr">&lt;<a =
href=3D"mailto:bitcoingrant@gmx.com" target=3D"_blank">bitcoingrant@gmx.com=
</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:so=
lid;padding-left:1ex">
<span style=3D"font-family:Verdana"><span style=3D"font-size:12px"><p dir=
=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span =
style=3D"background-color:transparent;white-space:pre-wrap;line-height:1.15=
">In brief, the authentication work as follows:</span><br>
</p><p style=3D"margin:0px;padding:0px">=C2=A0</p><p dir=3D"ltr" style=3D"l=
ine-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style=3D"vertical-a=
lign:baseline;font-variant:normal;font-style:normal;font-size:12px;white-sp=
ace:pre-wrap;background-color:transparent;text-decoration:none;font-family:=
Verdana;font-weight:normal">Server provides a token for the client to sign.=
</span></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;font-variant:normal;font-style:norma=
l;font-size:12px;white-space:pre-wrap;background-color:transparent;text-dec=
oration:none;font-family:Verdana;font-weight:normal">client passes the sign=
ed message and the bitcoin address back to the server.</span></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;font-variant:normal;font-style:norma=
l;font-size:12px;white-space:pre-wrap;background-color:transparent;text-dec=
oration:none;font-family:Verdana;font-weight:normal">server validates the m=
essage and honors the alias (optional) and bitcoin address as identificatio=
n.</span></p>
</span></span></blockquote><div><br></div><div><a href=3D"http://pilif.gith=
ub.io/2008/05/why-is-nobody-using-ssl-client-certificates/">http://pilif.gi=
thub.io/2008/05/why-is-nobody-using-ssl-client-certificates/</a></div></div=
>
</div></div>

--047d7b33cd7450651404ea314db3--