Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <k@old.school.nz>) id 1RdALC-0002g9-40 for bitcoin-development@lists.sourceforge.net; Wed, 21 Dec 2011 00:47:30 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of old.school.nz designates 209.85.212.47 as permitted sender) client-ip=209.85.212.47; envelope-from=k@old.school.nz; helo=mail-vw0-f47.google.com; Received: from mail-vw0-f47.google.com ([209.85.212.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RdALB-00010N-90 for bitcoin-development@lists.sourceforge.net; Wed, 21 Dec 2011 00:47:30 +0000 Received: by vbbfc21 with SMTP id fc21so7584929vbb.34 for <bitcoin-development@lists.sourceforge.net>; Tue, 20 Dec 2011 16:47:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.76.196 with SMTP id m4mr2192672vdw.112.1324428443743; Tue, 20 Dec 2011 16:47:23 -0800 (PST) Received: by 10.220.107.70 with HTTP; Tue, 20 Dec 2011 16:47:23 -0800 (PST) X-Originating-IP: [219.89.81.27] In-Reply-To: <4EEFAFFB.10508@parhelic.com> References: <CABr1YTebhitO4g-SarZ7H=aoG9a8zW1wd0rfR32o8i0vODbLJw@mail.gmail.com> <82659F61-0449-47BB-88DC-497E0D02F8A1@ceptacle.com> <CALxbBHUXEJLRDZ=RS1vuvkm7rDjFUPir0sU__f6TJXiTTQxWzA@mail.gmail.com> <4EEE58CA.5090902@justmoon.de> <4EEFAFFB.10508@parhelic.com> Date: Wed, 21 Dec 2011 13:47:23 +1300 Message-ID: <CA+QPp0pDWxq73uah72Y1ShbRS4FksU6VJFznDh6uSyh7G5mbhg@mail.gmail.com> From: Kyle Henderson <k@old.school.nz> To: Jordan Mack <jordanmack@parhelic.com> Content-Type: multipart/alternative; boundary=bcaec5015d07eb748704b48f861b X-Spam-Score: -0.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_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1RdALB-00010N-90 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Protocol extensions 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: Wed, 21 Dec 2011 00:47:30 -0000 --bcaec5015d07eb748704b48f861b Content-Type: text/plain; charset=UTF-8 > Developers could even choose to integrate Tor functionality into the > client itself at some point. > The "satoshi" bitcoin client already supports use over TOR with the proxy option - I think this was something Satoshi made regular use of. --bcaec5015d07eb748704b48f861b Content-Type: text/html; charset=UTF-8 <div></div><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Developers could even choose to integrate Tor functionality into the client itself at some point.<br> </blockquote><br>The "satoshi" bitcoin client already supports use over TOR with the proxy option - I think this was something Satoshi made regular use of.<br> --bcaec5015d07eb748704b48f861b--