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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1QlWZ6-0005nU-GT
for bitcoin-development@lists.sourceforge.net;
Tue, 26 Jul 2011 01:36:08 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me
designates 208.79.240.5 as permitted sender)
client-ip=208.79.240.5; envelope-from=bitcoin-list@bluematt.me;
helo=smtpauth.rollernet.us;
Received: from smtpauth.rollernet.us ([208.79.240.5])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1QlWZ5-0005N5-HD
for bitcoin-development@lists.sourceforge.net;
Tue, 26 Jul 2011 01:36:08 +0000
Received: from smtpauth.rollernet.us (localhost [127.0.0.1])
by smtpauth.rollernet.us (Postfix) with ESMTP id B962B59401A
for <bitcoin-development@lists.sourceforge.net>;
Mon, 25 Jul 2011 18:35:47 -0700 (PDT)
Received: from mail.bluematt.me (mail.bluematt.me [IPv6:2001:470:9ff2:2::13])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: @bluematt.me)
by smtpauth.rollernet.us (Postfix) with ESMTPSA
for <bitcoin-development@lists.sourceforge.net>;
Mon, 25 Jul 2011 18:35:47 -0700 (PDT)
Received: from [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b] (unknown
[IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b])
by mail.bluematt.me (Postfix) with ESMTPSA id DD1E72CF
for <bitcoin-development@lists.sourceforge.net>;
Tue, 26 Jul 2011 03:35:56 +0200 (CEST)
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <CAJ1JLts5_r6hHoJR-gS-CuuvS00p=RQ6iYbCyOkBDcvgs1xtew@mail.gmail.com>
References: <CAJ1JLts5_r6hHoJR-gS-CuuvS00p=RQ6iYbCyOkBDcvgs1xtew@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1";
protocol="application/pgp-signature";
boundary="=-uHHDaplK4tE7q/OUZIbR"
Date: Tue, 26 Jul 2011 03:35:56 +0200
Message-ID: <1311644156.29866.4.camel@Desktop666>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2
X-Rollernet-Abuse: Processed by Roller Network Mail Services. Contact
abuse@rollernet.us to report violations. Abuse policy:
http://rollernet.us/abuse.php
X-Rollernet-Submit: Submit ID 52cf.4e2e19f3.2b3ae.0
X-Spam-Score: -1.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 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1QlWZ5-0005N5-HD
Subject: Re: [Bitcoin-development] bitcoin DNS addresses
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: Tue, 26 Jul 2011 01:36:08 -0000
--=-uHHDaplK4tE7q/OUZIbR
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Mon, 2011-07-25 at 17:29 -0700, Rick Wesson wrote:
> I've just joined the list with the goals of producing a patch to
> sendtoaddress in rpc.cpp to support DNS lookups so that one could
> publish a TXT record in the DNS with their wallet address to
> facilitate sending of coin.
But...why?
Using URIs is much simpler and can be more useful in terms of being able
to give different addresses and/or values per user.
Also, despite DNSSec being "out there" DNS is still very insecure to
transmit something that will result in money transfer...some idiot tries
it on public WiFi and a MITM steals your coins...DNS is really just not
well suited for this kind of thing.
If you want nice name->address mapping, a simple HTTPS server with
addresses and client support (there are some patches around for this)
works much better in the end.
--=-uHHDaplK4tE7q/OUZIbR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAABAgAGBQJOLhn6AAoJEBrh01BD4I5UG+sP/RWfeJ0FXkLQLRXE1YpxoMph
8AiYgJ4lye9PAPpcRkFf4xPBlIT9AE3b9El/kL5exoKlmlRxZBKvkL96Gpx0u1qL
bItKtEMgRiXgRtbuq9BPDbCLuCaiqE54q+mM4d2ae4AiodlQ2muiHBNSOp/GTDnp
slwE+Vykh4dxUat+hrgPfpA80xXokuSRFU8p9TkQ4wySj2vIlWiOsXbfuy6zV8Co
MnPpTweqo1C5KvKxsNnR+HJMUcTvsPvY3oFJeECRL73uvGel5uIUn7r1xAAR9JJL
AK8CN6rTpVbEy2JRSo6ycux4DnhbVSjd2Q7Rh7W58bxnhd9/Cs+A4JAonCMcCBaJ
uxqlq0somMgcFEeYtCEXzuplVd4CAEIrWNlw5kv25OdqCDQ+3NJ9uhCgxBXNSzNF
ev6cOyzo3+eimfYpF/WVr1FlVIj3/WHv6DFrh3M0VR8v+34SSndNzcLV5yVDjRbu
DGOkMX6WXDCwwcHnd+x1e03Prhtaabo4TxCo5k76fRWFIA8maJXmKKUs1AcInSJT
Y7i129tCSioY+YGJhZh2gE3zcBJ8DBNhXnymj/Oaas0eXHxyPUvD1R4n/icUi0a/
v+gGbhfY+WidZfVWxTde1OeeGTcW4gc4i7Cj2gPG0eWohJ4FdfpkictuRWHfNbN+
HzcBsBB/MCAXrEGmyMmB
=Wgq9
-----END PGP SIGNATURE-----
--=-uHHDaplK4tE7q/OUZIbR--
|
