From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QlZAg-0003BQ-2r for bitcoin-development@lists.sourceforge.net; Tue, 26 Jul 2011 04:23:06 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1QlZAb-0007Jx-5Z for bitcoin-development@lists.sourceforge.net; Tue, 26 Jul 2011 04:23:06 +0000 Received: from ishibashi.localnet (fl-67-77-87-241.dhcp.embarqhsd.net [67.77.87.241]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 8F0A8D707D8; Tue, 26 Jul 2011 04:22:51 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 26 Jul 2011 00:22:21 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.4; x86_64; ; ) References: <1311644156.29866.4.camel@Desktop666> In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107260022.24961.luke@dashjr.org> X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.6 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QlZAb-0007Jx-5Z Subject: Re: [Bitcoin-development] bitcoin DNS addresses X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 04:23:06 -0000 On Monday, July 25, 2011 11:35:34 PM Rick Wesson wrote: > I started from the premise that I can't remember a bitcoin address but > I can/do remember email addresses which, as an identity are easy > labels for humans to remember. The IPv4 address is the metaphor I > consider. As someone who actually worked on parts of DNSSEC I do > believe in it -- and that it offers reasonable security for > transactions. 1. Right now you practically need a unique Bitcoin address per transaction. 2. DNSSEC is on the edge of becoming illegal in the US. 3. Emails aren't merely domains. I would propose something like resolving foo@bar.net to a SRV lookup for _bitcoinaddressresolution._tcp.foo.bar.net, expecting a cert for bar.net, making a HTTPS request for /bitcoinaddressresolution?foo@bar.net, and also sending an email to foo@bar.net (the usual way) signed with the keys used for the transaction. ;)