From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RaUaF-0000cb-8e for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 15:47:59 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RaUa9-0007pI-HA for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 15:47:59 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 1ABE0560514; Tue, 13 Dec 2011 15:47:48 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 13 Dec 2011 10:47:42 -0500 User-Agent: KMail/1.13.7 (Linux/3.1.4-gentoo; KDE/4.6.5; x86_64; ; ) References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com> 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: <201112131047.43569.luke@dashjr.org> X-Spam-Score: -2.1 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RaUa9-0007pI-HA Cc: Jorge Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases 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, 13 Dec 2011 15:47:59 -0000 On Tuesday, December 13, 2011 8:06:15 AM Gavin Andresen wrote: > I agree with Mike Hearn and Christian Decker-- paying to > 'somebody@foo.com' should become, behind the scenes, a HTTPS query to > https://foo.com/something. If you just want to (say) donate to > eff.org, then paying to '@eff.org' aught to work nicely. Seems like introducing a gaping security risk to me. > It seems to me that if it was DNS-based, the address should be > something like 'somebody.bitcoin.foo.com'. But I think it is unlikely > people will setup and run a custom DNS server just to support bitcoin > payments. Could always use a fixed address and email somebody@foo.com a signed message.