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 ) 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: References: <4f55608991d5377117ecf1728cd8db0c.squirrel@fruiteater.riseup.net> Date: Sun, 6 Jul 2014 23:54:23 -0700 From: "Odinn Cyberguerrilla" To: "Wladimir" 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 06:54:31 -0000 > On Mon, Jul 7, 2014 at 8:34 AM, Odinn Cyberguerrilla > 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.