1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1X42i4-00052S-Dx
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Jul 2014 06:47:32 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.175 as permitted sender)
client-ip=209.85.213.175; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f175.google.com;
Received: from mail-ig0-f175.google.com ([209.85.213.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X42i2-0002dU-CZ
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Jul 2014 06:47:32 +0000
Received: by mail-ig0-f175.google.com with SMTP id h3so10452703igd.8
for <bitcoin-development@lists.sourceforge.net>;
Sun, 06 Jul 2014 23:47:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.77.34 with SMTP id p2mr37304500igw.31.1404715642363; Sun,
06 Jul 2014 23:47:22 -0700 (PDT)
Received: by 10.64.60.195 with HTTP; Sun, 6 Jul 2014 23:47:22 -0700 (PDT)
In-Reply-To: <4f55608991d5377117ecf1728cd8db0c.squirrel@fruiteater.riseup.net>
References: <CA+s+GJDSPS=zsM64wHaG1CucHVkO==L1QkHYiciUo9iJ-RADng@mail.gmail.com>
<CA+s+GJAei15doCg-h2BK6tEvfwy5m5YHPhg_+8b=G4ew41Mqjw@mail.gmail.com>
<4f55608991d5377117ecf1728cd8db0c.squirrel@fruiteater.riseup.net>
Date: Mon, 7 Jul 2014 08:47:22 +0200
Message-ID: <CA+s+GJDPnz-JYbhTZw2cLVb1QrerrHVim9GRBdgVPsOeTLFJ+Q@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Odinn Cyberguerrilla <odinn.cyberguerrilla@riseup.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1X42i2-0002dU-CZ
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:47:32 -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
|
