summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRick Wesson <rick@support-intelligence.com>2011-07-25 21:54:23 -0700
committerbitcoindev <bitcoindev@gnusha.org>2011-07-26 04:54:29 +0000
commit0ee6da37c90096bcce9a83594d339fd83edff3c0 (patch)
tree090f891edb5d94c2459bca0aa6c7a16017ccc326
parent4fc7f095e94243bd83eb4fb41ec230f1230b4936 (diff)
downloadpi-bitcoindev-0ee6da37c90096bcce9a83594d339fd83edff3c0.tar.gz
pi-bitcoindev-0ee6da37c90096bcce9a83594d339fd83edff3c0.zip
Re: [Bitcoin-development] bitcoin DNS addresses
-rw-r--r--2b/d391744cb6db7b80046db420ea7034a810d35374
1 files changed, 74 insertions, 0 deletions
diff --git a/2b/d391744cb6db7b80046db420ea7034a810d353 b/2b/d391744cb6db7b80046db420ea7034a810d353
new file mode 100644
index 000000000..6276044f5
--- /dev/null
+++ b/2b/d391744cb6db7b80046db420ea7034a810d353
@@ -0,0 +1,74 @@
+Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
+ helo=mx.sourceforge.net)
+ by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <rick.wesson@iidf.org>) id 1QlZf3-0005ga-R8
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 26 Jul 2011 04:54:29 +0000
+X-ACL-Warn:
+Received: from mail-yx0-f175.google.com ([209.85.213.175])
+ by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1QlZf2-0002Pp-Qd
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 26 Jul 2011 04:54:29 +0000
+Received: by yxi19 with SMTP id 19so38748yxi.34
+ for <bitcoin-development@lists.sourceforge.net>;
+ Mon, 25 Jul 2011 21:54:23 -0700 (PDT)
+MIME-Version: 1.0
+Received: by 10.150.193.15 with SMTP id q15mr5388838ybf.240.1311656063282;
+ Mon, 25 Jul 2011 21:54:23 -0700 (PDT)
+Received: by 10.151.114.15 with HTTP; Mon, 25 Jul 2011 21:54:23 -0700 (PDT)
+In-Reply-To: <201107260022.24961.luke@dashjr.org>
+References: <CAJ1JLts5_r6hHoJR-gS-CuuvS00p=RQ6iYbCyOkBDcvgs1xtew@mail.gmail.com>
+ <1311644156.29866.4.camel@Desktop666>
+ <CAJ1JLts9vcF7bGo8udK9OicWhAUHvmeFDrZQDKBoGQbp-nYGrw@mail.gmail.com>
+ <201107260022.24961.luke@dashjr.org>
+Date: Mon, 25 Jul 2011 21:54:23 -0700
+Message-ID: <CAJ1JLttnARz=f0UmzJKpCXpMeKg1X_R7Jfwv7tZq_pJqn8LbQQ@mail.gmail.com>
+From: Rick Wesson <rick@support-intelligence.com>
+To: Luke-Jr <luke@dashjr.org>
+Content-Type: text/plain; charset=ISO-8859-1
+X-Spam-Score: 0.7 (/)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+ 0.7 AWL AWL: From: address is in the auto white-list
+X-Headers-End: 1QlZf2-0002Pp-Qd
+Cc: bitcoin-development@lists.sourceforge.net
+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 04:54:29 -0000
+
+>
+> 1. Right now you practically need a unique Bitcoin address per transaction.
+
+I'd like to find ways to alievate this requirement.
+
+> 2. DNSSEC is on the edge of becoming illegal in the US.
+
+really, pointers please. DHS was a huge funder for DNSSEC asn .mil was
+the first domain to deploy it. I think you may be miss-informed.
+
+> 3. Emails aren't merely domains.
+
+correct, I was speaking about an "address" that used the same/simular
+formatting but did not use the SMTP protocol.
+
+-rick
+
+> 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. ;)
+>
+
+