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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1Wukd3-0005xp-Um
for bitcoin-development@lists.sourceforge.net;
Wed, 11 Jun 2014 15:39:58 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.176 as permitted sender)
client-ip=209.85.213.176; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f176.google.com;
Received: from mail-ig0-f176.google.com ([209.85.213.176])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wukd3-0005AA-7r
for bitcoin-development@lists.sourceforge.net;
Wed, 11 Jun 2014 15:39:57 +0000
Received: by mail-ig0-f176.google.com with SMTP id a13so6549810igq.9
for <bitcoin-development@lists.sourceforge.net>;
Wed, 11 Jun 2014 08:39:51 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.100.195 with SMTP id b3mr3168605ico.94.1402501191351;
Wed, 11 Jun 2014 08:39:51 -0700 (PDT)
Received: by 10.64.60.195 with HTTP; Wed, 11 Jun 2014 08:39:51 -0700 (PDT)
Date: Wed, 11 Jun 2014 17:39:51 +0200
Message-ID: <CA+s+GJDSPS=zsM64wHaG1CucHVkO==L1QkHYiciUo9iJ-RADng@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.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: 1Wukd3-0005AA-7r
Subject: [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: Wed, 11 Jun 2014 15:39:58 -0000
Hello all,
Is anyone using a SOCKS4-only proxy with Bitcoin Core? SOCKS5 was
introduced in 1996, so there is hardly an excuse to not support it.
If no one screams fire, we plan on removing support for it in the next
major release, for two reasons:
- It would remove some crufty, hardly tested code paths
- SOCKS5 offers better privacy as it allows DNS redirection
Wladimir
|
