summaryrefslogtreecommitdiff
path: root/e2/91c4a634dac214fdd6374addeba4fcf577584b
blob: 20b8adbbc4f294cec0e952a93e01bd5221eb6097 (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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@bitpay.com>) id 1VcegG-0001zh-32
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 Nov 2013 17:08:12 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.212.182 as permitted sender)
	client-ip=209.85.212.182; envelope-from=jgarzik@bitpay.com;
	helo=mail-wi0-f182.google.com; 
Received: from mail-wi0-f182.google.com ([209.85.212.182])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VcegF-0000E6-2z
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 Nov 2013 17:08:12 +0000
Received: by mail-wi0-f182.google.com with SMTP id ez12so2251897wid.3
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 02 Nov 2013 10:08:04 -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:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=NtjcFoxYJSVrFhF9kYCudNsFXBEMFUK7kntgK5E8GkA=;
	b=XxZ8+/EtsHs/9GFzj+0/pINU76UWfhuBlfz5WnplErFNOZMmN3/O0fIehlKRP6+tCC
	Gj26TD6h9V0gjGqFmH7mMbMRwdRC5A6uTaqG4x9ZITY+wbi0dR7SiuKMQJYF5n0irweP
	2NF2eRAvqUc6A26wx/sFsW3o0GNHcFNFUN0FWOtNiAHXh19eJDuEJcpT2z3s5IsRYDOp
	6/786TQpqsQiAE6B3JJgHxywuoiaWOQBfJc37dV0hl2jK2tMB0fvsMlwZqlHOMK4pbXH
	ziI8fjWV71AiSWPPW2GVyZUXFaESW9T6mo3Pyf7dmcU8LFTYmr9g2zd5K2myZkRXOPY2
	Rgog==
X-Gm-Message-State: ALoCoQmEru1B3X2GycPhN2AuSVe0VAlD8BHaBA3ziDq1AIJtaXuRT84zJ6W1m1u970fcCxF7SAjd
MIME-Version: 1.0
X-Received: by 10.180.11.37 with SMTP id n5mr6309915wib.25.1383412084816; Sat,
	02 Nov 2013 10:08:04 -0700 (PDT)
Received: by 10.194.164.164 with HTTP; Sat, 2 Nov 2013 10:08:04 -0700 (PDT)
In-Reply-To: <CAKaEYhKkWGYOGrbmTtziBsDjz3wMPoPWKtfQs6bEK8-a-sfpyw@mail.gmail.com>
References: <20131102050144.5850@gmx.com>
	<CANEZrP2UwEX+u0XCxmaMaRWqVMr+3E63UYnVz9oMubbsiJU+6A@mail.gmail.com>
	<5274FBF7.90301@iki.fi>
	<CANEZrP2N1DRBcN4JuXKJAodKwk=qNk5hiSnLyx1vbQ1gAd=EhQ@mail.gmail.com>
	<CAKaEYhKkWGYOGrbmTtziBsDjz3wMPoPWKtfQs6bEK8-a-sfpyw@mail.gmail.com>
Date: Sat, 2 Nov 2013 13:08:04 -0400
Message-ID: <CAJHLa0N5V44zC-QgYKMNNLgeNy96xLJSp2RTFjQwAhX9AweOXg@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
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 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	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
	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: bitcoin.it]
X-Headers-End: 1VcegF-0000E6-2z
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 17:08:12 -0000

On Sat, Nov 2, 2013 at 12:52 PM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> Identity need not be a hard problem.  In my view it is a solved problem.


Yes:  https://en.bitcoin.it/wiki/Identity_protocol_v1