summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOdinn Cyberguerrilla <odinn.cyberguerrilla@riseup.net>2014-07-06 23:54:23 -0700
committerbitcoindev <bitcoindev@gnusha.org>2014-07-07 06:54:30 +0000
commit8dc4ef4f45f8f5cf64cb455e393a033dab506467 (patch)
tree261502dafb415c6a22a1452d1d7465d8de7e597c
parent7485cec57df6552a3a2c70b17e65d5575027586e (diff)
downloadpi-bitcoindev-8dc4ef4f45f8f5cf64cb455e393a033dab506467.tar.gz
pi-bitcoindev-8dc4ef4f45f8f5cf64cb455e393a033dab506467.zip
Re: [Bitcoin-development] Anyone still using SOCKS4?
-rw-r--r--42/c38cba7645051f18cff957bc1cbb6768291f5597
1 files changed, 97 insertions, 0 deletions
diff --git a/42/c38cba7645051f18cff957bc1cbb6768291f55 b/42/c38cba7645051f18cff957bc1cbb6768291f55
new file mode 100644
index 000000000..722ae7769
--- /dev/null
+++ b/42/c38cba7645051f18cff957bc1cbb6768291f55
@@ -0,0 +1,97 @@
+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 <odinn.cyberguerrilla@riseup.net>) id 1X42oo-00028H-V4
+ for bitcoin-development@lists.sourceforge.net;
+ Mon, 07 Jul 2014 06:54:30 +0000
+Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of riseup.net
+ designates 198.252.153.129 as permitted sender)
+ client-ip=198.252.153.129;
+ envelope-from=odinn.cyberguerrilla@riseup.net;
+ helo=mx1.riseup.net;
+Received: from mx1.riseup.net ([198.252.153.129])
+ by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
+ (Exim 4.76) id 1X42on-0004ra-78
+ for bitcoin-development@lists.sourceforge.net;
+ Mon, 07 Jul 2014 06:54:30 +0000
+Received: from fruiteater.riseup.net (fruiteater-pn.riseup.net [10.0.1.74])
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
+ (Client CN "*.riseup.net",
+ Issuer "Gandi Standard SSL CA" (not verified))
+ by mx1.riseup.net (Postfix) with ESMTPS id 51D014ACDC;
+ Sun, 6 Jul 2014 23:54:23 -0700 (PDT)
+Received: from [127.0.0.1] (localhost [127.0.0.1])
+ (Authenticated sender: odinn.cyberguerrilla@fruiteater.riseup.net)
+ with ESMTPSA id EF14EE63
+Received: from localhost (127.0.0.1)
+ (SquirrelMail authenticated user odinn.cyberguerrilla)
+ by fruiteater.riseup.net with HTTP; Sun, 6 Jul 2014 23:54:23 -0700
+Message-ID: <482f7271864acb611912b0ed901ad601.squirrel@fruiteater.riseup.net>
+In-Reply-To: <CA+s+GJDPnz-JYbhTZw2cLVb1QrerrHVim9GRBdgVPsOeTLFJ+Q@mail.gmail.com>
+References: <CA+s+GJDSPS=zsM64wHaG1CucHVkO==L1QkHYiciUo9iJ-RADng@mail.gmail.com>
+ <CA+s+GJAei15doCg-h2BK6tEvfwy5m5YHPhg_+8b=G4ew41Mqjw@mail.gmail.com>
+ <4f55608991d5377117ecf1728cd8db0c.squirrel@fruiteater.riseup.net>
+ <CA+s+GJDPnz-JYbhTZw2cLVb1QrerrHVim9GRBdgVPsOeTLFJ+Q@mail.gmail.com>
+Date: Sun, 6 Jul 2014 23:54:23 -0700
+From: "Odinn Cyberguerrilla" <odinn.cyberguerrilla@riseup.net>
+To: "Wladimir" <laanwj@gmail.com>
+User-Agent: SquirrelMail/1.4.21
+MIME-Version: 1.0
+Content-Type: text/plain;charset=utf-8
+X-Priority: 3 (Normal)
+Importance: Normal
+X-Virus-Scanned: clamav-milter 0.98.1 at mx1
+X-Virus-Status: Clean
+Content-Transfer-Encoding: quoted-printable
+X-Spam-Score: -2.0 (--)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+ -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
+ no trust [198.252.153.129 listed in list.dnswl.org]
+ -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
+ -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
+ domain
+ 0.1 DKIM_SIGNED Message has a DKIM or DK signature,
+ not necessarily valid
+ 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
+ 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
+ lines
+X-Headers-End: 1X42on-0004ra-78
+Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
+Subject: Re: [Bitcoin-development] Anyone still using SOCKS4?
+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: Mon, 07 Jul 2014 06:54:31 -0000
+
+> On Mon, Jul 7, 2014 at 8:34 AM, Odinn Cyberguerrilla
+> <odinn.cyberguerrilla@riseup.net> wrote:
+>> Wait, I thought SOCKS4 was supposed to help somehow in terms of
+>> prevention
+>> of leaking of information?
+>
+> SOCKS4a (unlike SOCKS4) supports doing DNS lookups on the server, but
+> it is not supported by bitcoin core. So it is not part of this
+> discussion.
+>
+> And SOCKS5 can do all of that just as well. But if you feel like
+> contributing SOCKS4a support that's fine with me.
+>
+> Wladimir
+>
+
+OK, thanks Wladimir.
+
+
+