blob: d88239a862bf1a5882e684dcbf3403b2a6bbed74 (
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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <theymos@mm.st>) id 1RbHSU-0003Jc-5g
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 19:59:14 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of mm.st
designates 66.111.4.27 as permitted sender)
client-ip=66.111.4.27; envelope-from=theymos@mm.st;
helo=out3.smtp.messagingengine.com;
Received: from out3.smtp.messagingengine.com ([66.111.4.27])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1RbHST-0005RJ-Af
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 19:59:14 +0000
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45])
by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 72C0C21757
for <bitcoin-development@lists.sourceforge.net>;
Thu, 15 Dec 2011 14:59:07 -0500 (EST)
Received: from web3.nyi.mail.srv.osa ([10.202.2.213])
by compute5.internal (MEProxy); Thu, 15 Dec 2011 14:59:07 -0500
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
id 4E7C84008F; Thu, 15 Dec 2011 14:59:07 -0500 (EST)
Message-Id: <1323979147.27319.140661012141129@webmail.messagingengine.com>
X-Sasl-Enc: 9+AK/cJUbsradJrdiG1ECmJRKYAw6+flZdEtkQd/vOwe 1323979147
From: "theymos" <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Mailer: MessagingEngine.com Webmail Interface
References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com>
In-Reply-To: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com>
Date: Thu, 15 Dec 2011 13:59:07 -0600
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(theymos[at]mm.st)
-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
X-Headers-End: 1RbHST-0005RJ-Af
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
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: Thu, 15 Dec 2011 19:59:14 -0000
Bitcoin already has code and a protocol for transactions to IP
addresses. Why not reuse that for dynamic address lookup? Just a few
changes are necessary to enable complete user@server.com handling:
- Extend the protocol so that "reply" messages can be signed by a fixed
public key
- Extend "checkorder" messages so they can specify an account to
send BTC to. Or standardize on how to put the account into the
message field.
- Enable DNS lookups for IP transactions. The DNS-only proposals could
also be used here to avoid having to use the IP transaction protocol
sometimes. The public key for signing "reply" messages can be gotten
from TXT records. This will be safe with DNSSEC and Namecoin. With
plain DNS Bitcoin could take a SSH-like approach and ask the user to
verify the public key the first time it is used, remembering it later.
DoS attacks are already handled by the IP transactions code: the same IP
address is always given the same bitcoin address until it pays to that
bitcoin address.
|
